#18756: Use coerce actions in the category framework
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.8
Component: coercion | Resolution:
Keywords: cython, coercion, | Merged in:
actions, categories | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: | e1111c346a82639bb41161469754d45008117801
u/SimonKing/combinatorial_free_module_cython_coercion| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by tscrim):
This also seems like it might solve #15947. Although perhaps we could use
the idea that we can specify a class in the category that all elements of
that category inherit from?
However I'm not sure about the initial post about overriding
`_acted_upon_` would break scalar multiplication. Couldn't we just require
that the user makes a super call at the end if they still want the scalar
multiplication (such as for `_get_action_` or `_coerce_map_from_`)? IMO,
this would hardly an extraordinary requirement, and currently seems like a
requirement for `_get_action_` in the current proposal.
--
Ticket URL: <http://trac.sagemath.org/ticket/18756#comment:21>
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.
