#11935: Make parent/element classes independent of base rings
------------------------------------------------------------------+---------
Reporter: SimonKing |
Owner:
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-5.10
Component: categories |
Resolution:
Keywords: parent class, element class, category | Work
issues:
Report Upstream: N/A |
Reviewers: Nicolas Thiery, Travis Scrimshaw
Authors: Simon King | Merged
in:
Dependencies: #9138, #11900, #11943, #12875, #12876, #12877 |
Stopgaps:
------------------------------------------------------------------+---------
Comment (by SimonKing):
Replying to [comment:104 SimonKing]:
> So, question: Do you think that this model is the way to go? It keeps
abstract and concrete classes neatly apart, it will reduce the need to
have custom `X._Hom_(...)`, and we could get rid of the hack with
`__new__`.
I think I should first try to review #12876 (which is a dependency
anyway). There, you state:
* Unified the logic for selecting the class when building a Homset (e.g.
Homset, `RingHomset`, `HeckeModuleHomspace`, ...). This is now
systematically done through the _Hom_ hook. The logic still has a
fundamental flaw, but that's for the later #10668.
So, you want that it is through the `_Hom_` hook---let me guess (haven't
read it yet): `_Hom_` will play a similar role to Hom as
`_element_constructor_` plays to `__call__`...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11935#comment:105>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
