#15927: What are the requirements on super_categories?
----------------------------------+------------------------
Reporter: darij | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.3
Component: categories | Resolution:
Keywords: C3, categories | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------+------------------------
Comment (by darij):
My example in the ticket description is probably not representative: it is
not some indirect redundancy, but just a duplicate entry in
`super_categories`. The C3 algorithm doesn't like this, and I kind of
understand it. I have pushed some documentation about it onto the #10963
branch.
It remains to be seen whether
1) we want to change this behavior. (Is there a situation in which some
category takes another category's `super_categories` list and appends more
stuff to it without checking if that stuff is already in it? If so, it
needs to be changed.)
2) there are some issues with indirect redundancy as well (which then
really have to be fixed).
--
Ticket URL: <http://trac.sagemath.org/ticket/15927#comment:5>
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.
