#16507: Better handling of subspace construction in pushout
-------------------------------------+-------------------------------------
Reporter: pbruin | Owner:
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: categories | Resolution:
Keywords: pushout subspace, | Merged in:
sd59 | Reviewers:
Authors: Peter Bruin, | Work issues:
Robert Bradshaw | Commit:
Report Upstream: N/A | e31574828e020c03ff883856868ee089e95c3ec3
Branch: | Stopgaps:
u/robertwb/ticket/16507 |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by pbruin):
Replying to [comment:6 SimonKing]:
> I hope this will not end up with a pullback construction.
It definitely won't; this algorithm is far from being symmetric.
> Isn't it the case that one can simply drop all "reversed" construction
functors, ''before'' constructing the pushout?
In that case you would end up with some object admitting coercion maps
from both original objects, but the idea is to try to get something as
close as possible to the "real" push-out. Hopefully Robert's list of
examples makes it clear that one shouldn't just throw away all "coercion-
reversed" constructions.
--
Ticket URL: <http://trac.sagemath.org/ticket/16507#comment:11>
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.