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
@EmilyBourne proposes to simplify the Matrix API with an intermediate MatrixLapack class and specialized solve_inplace for MatrixSparse and MatrixLapack.
solve_inplace_method would be removed or defined independently in MatrixLapack and MatrixSparse, but won't be a virtual function of Matrix anymore
The text was updated successfully, but these errors were encountered:
I am not sure that this is a duplicate. Issues are for defining work to be done while discussions are about finding the right approach so an issue can be described. That said there is definitely a large overlap. I think we should probably edit and re-open this issue once a conclusion has been reached about the right interface to use
@EmilyBourne proposes to simplify the Matrix API with an intermediate
MatrixLapack
class and specializedsolve_inplace
forMatrixSparse
andMatrixLapack
.solve_inplace_method
would be removed or defined independently inMatrixLapack
andMatrixSparse
, but won't be a virtual function ofMatrix
anymoreThe text was updated successfully, but these errors were encountered: