#16399: Matrix stack doesn't coerce to a common parent
-------------------------------------+-------------------------------------
Reporter: tscrim | Owner: tscrim
Type: defect | Status: new
Priority: major | Milestone: sage-6.4
Component: coercion | Resolution:
Keywords: matrix stack | Merged in:
coercion | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: u/chapoton/16399 | 9986c476c78510e1b98d46890a5b9506f3b62613
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:5 nbruin]:
> Given the syntax, `m.stack(...)` it makes a lot of sense to try and let
the result depend as much as possible on m and not on "...".
I disagree with this. That's just a pure syntactical thing, mathematically
"stacking" could be seen as a binary operator.
I am +1 to coercion, but there could indeed be unexpected consequences.
--
Ticket URL: <http://trac.sagemath.org/ticket/16399#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
