#15573: (co)product coercion
-------------------------------------+-------------------------------------
Reporter: elixyre | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.1
Component: categories | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/elixyre/ticket/15573 | 76f28279aed8534bcdfb14f8f7c7845598b3a50e
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by tscrim):
I think whatever is returned by `a_realization()` should have a
(co)product/antipode/etc. methods implemented. If not, the code should
call the "best" realization to do the computations in by overwriting the
respective `*_by_coercion()` in either the realization category or in the
parent directly (sometimes [often] the change-of-basis is nontrivial as
well). Although this requirement that `a_realization()` has a concrete
implementation of the operation methods (or it's elements) is not stated
and it should be.
However, `+1` that there should be a `*_by_coercion()` in the most general
(realization) category that defines that operation. IMO the
`coproduct_by_coercion()` method in this ticket should go in `Coalgebras`,
in which `coproduct()` will need some tweaks since it seems to be assuming
a basis. Similarly `product_by_coercion()` is inherited from the `Magmas`
category and is redundant.
Best,[[BR]]
Travis
--
Ticket URL: <http://trac.sagemath.org/ticket/15573#comment:4>
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/groups/opt_out.
