#13589: Controlling C3 to solve once for all the Method Resolution Order issues
for
category classes
----------------------------------------------------------+-----------------
Reporter: nthiery | Owner:
nthiery
Type: defect | Status:
needs_review
Priority: major | Milestone:
sage-5.10
Component: categories | Resolution:
Keywords: method resolution order, C3 | Work issues:
Report Upstream: N/A | Reviewers:
Simon King, Florent Hivert
Authors: Nicolas M. Thiéry | Merged in:
Dependencies: #13501, #12894, #12876, #11935, #12895 | Stopgaps:
----------------------------------------------------------+-----------------
Comment (by nthiery):
Replying to [comment:28 nthiery]:
> While playing with larger hierarchy of classes for the functorial
construction patch, I stumbled on one execution path which was not treated
correctly. I'll post an updated patch shortly.
Ok, the updated patch includes the (hopefuly) now correct implementation
together with relevant tests. At this occasion, I declared a couple more
variables for cython and added some debugging code (commented out by
default).
You can look at :attachment:c3-fix-nt.patch if you just want to see the
changes.
I guess last time I wrote such a long function was when I played around
with F5! It would be a good candidate for a computer assisted proof of
correctness or for automatic test generation.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13589#comment:29>
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.
