#12778: Incorrect coercion of matrix elements when from different rings
----------------------------------+-----------------------------------------
Reporter: kcrisman | Owner: jason, was
Type: defect | Status: new
Priority: major | Milestone: sage-5.0
Component: linear algebra | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by kcrisman):
Got it. In sage.matrix.constructor.py:
{{{
entries = []
for v in args[0]:
entries.extend(v)
}}}
is how the list is created. Then `prepare` is used to make this into a
list and base ring, and that is where `Sequence` is used.
But the problem is that this means it takes the whole flattened list of
entries in the matrix and does the step-by-step sequence construction.
We could just have it find the universe for the sequence and then make the
sequence again. That could be a big slowdown, though. On the other hand,
if someone is not specifying the ring ahead of time (this all happens only
if {{{elif len(args) == 1:}}} then they probably aren't as interested in
speed, are they?
Thoughts?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12778#comment:7>
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.
