You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use "set" function, you let element be pushed back directly. However, due to codes in operational functions like add or subtract, it seems that you need elements to be ordered. So should it be correct that you need to reorder elements when you set a new element?
When it comes to "add" function, why "this->m_rows != mat.cols()"? shouldn't it be "!=mat.rows()" because we need't to transpose a matrix when sum two matrices together?
The text was updated successfully, but these errors were encountered:
When we use "set" function, you let element be pushed back directly. However, due to codes in operational functions like add or subtract, it seems that you need elements to be ordered. So should it be correct that you need to reorder elements when you set a new element?
When it comes to "add" function, why "this->m_rows != mat.cols()"? shouldn't it be "!=mat.rows()" because we need't to transpose a matrix when sum two matrices together?
The text was updated successfully, but these errors were encountered: