#12808: Optimize ClassCallMetaClass using Cython
--------------------------------------------------+-------------------------
Reporter: hivert | Owner: jason
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.0
Component: misc | Resolution:
Keywords: classcall UniqueRepresentation | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Florent Hivert | Merged in:
Dependencies: | Stopgaps:
--------------------------------------------------+-------------------------
Comment (by hivert):
Replying to [comment:6 SimonKing]:
> This is (I guess) why `ClasscallMetaclass` inherits from
`NestedMetaclass`. But Ticket #11794 provides examples for a different and
more skalable solution: ''Make metaclasses dynamic!''
Yes it is. We discussed last week with Nicolas of switching the
inheritance
order here. That is using only `NestedMetaclass` for Categories. I still
have
to check that this doesn't break pickling of Parent with a nested Element.
> So, what I mean by a generalised metaclass framework in Sage is:
> * Implement a base class `SageMetaclass`, from which all metaclasses
(such as `NestedMetaclass` and `ClasscallMetaclass` and
`FastHashMetaclass`) are derived.
> * Make it so that if A, B, C are classes with different metaclasses
(all derived from `SageMetaclass`) can be used as base classes for a new
class. In that way, the features provided by metaclasses could be freely
combined.
>
> But I guess that's a topic for a different ticket...
+1 for this and for keeping it for a different ticket.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12808#comment:9>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
