#13012: MatrixSpace is too eager to construct zero matrices
--------------------------------------+-------------------------------------
Reporter: novoselt | Owner: jason, was
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.1
Component: linear algebra | Resolution:
Keywords: sd40.5 | Work issues: doctests
Report Upstream: N/A | Reviewers:
Authors: Andrey Novoseltsev | Merged in:
Dependencies: | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by novoselt):
Not yet finished, but I am doing the following:
* concentrate matrix constructor code in `MatrixSpace.matrix` (currently
a lot is done in its `__call__`);
* quit automatic determination of "data as columns" - this is dangerous
since if the code relying on it ever hits a square matrix, it will give a
hard to find mistake;
* drop support for constructing matrices from arbitrary combination of
matrices/vectors/scalars introduced at #10628 (and released in Sage-5.0).
This was not the goal of that ticket and I think it is a dangerous
functionality since it easily lets through wrong code on "corner cases":
those who deliberately want to augment or stack matrices should use
corresponding methods.
If you object to anything on this list, please talk to me! I think that
correctness of this approach is indirectly confirmed by the fact that only
tests in `matrix_space` that demonstrate removed functionality fail in the
matrix directory (a few tests fail because of a more informative error
message).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13012#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
