#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 nthiery):
I very much like the declarative approach.
Just wondering:
- Should there be two separate tickets: one for better support for
coercions in categories, and the other for the Cythonizing of CFM (the two
are relatively independent of each other)?
- Since there is some file moving anyway, what about using the occasion to
move the .pyx file directly in `sage.modules.with_basis.free_module` (with
just a link `sage.combinat.free_module.CombinatorialFreeModule` ->
`sage.modules.with_basis.free_module.FreeModule` for backward
compatibility)?
Thanks!
--
Ticket URL: <http://trac.sagemath.org/ticket/18756#comment:16>
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.
