#15927: What are the requirements on super_categories?
----------------------------------+------------------------
Reporter: darij | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.2
Component: categories | Resolution:
Keywords: C3, categories | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------+------------------------
Comment (by nthiery):
Thanks for creating the ticket. I see the point, though as far as I
remember, I never got hit by that myself; hence I would not call this
urgent.
Also, except for the primer documentation, it's completely orthogonal to
#10963.
An obvious approach would be to change the lazy_attribute
Category._super_categories, replacing the sort by a call to
Category._sort_uniq. Feel free to experiment with that! A priori, I bet
all test will still pass. Now there remains to check that there is no
performance hit, and double check that everything goes through this
attribute. This can be tested with or without #10963.
Cheers,
Nicolas
--
Ticket URL: <http://trac.sagemath.org/ticket/15927#comment:3>
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.
