-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dense + sparse matrix should be dense #29359
Comments
comment:1
Moving tickets to milestone sage-9.2 based on a review of last modification date, branch status, and severity. |
comment:2
The problem here seems to be that there is a coercion from the dense matrix space to the sparse one, so the sparse matrix space is discovered as a common parent:
It would be better if the pushout were used here, as it correctly results in a dense matrix space:
|
comment:4
more information:
|
comment:5
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
When adding or subtracting a dense matrix and a sparse matrix, the resulting matrix is sparse in some cases.
This seems to happen when the rings are different and the common coercion parent of the rings is the ring of the sparse matrix.
Component: coercion
Issue created by migration from https://trac.sagemath.org/ticket/29359
The text was updated successfully, but these errors were encountered: