#18109: Restructure IntegerListLex code
-------------------------------------+-------------------------------------
Reporter: vdelecroix | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.6
Component: combinatorics | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/ticket/18109 | 9582a7a5248f609a2d2de02497b4b1d36d9dd96e
Dependencies: #18181, #18184 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by nthiery):
Good morning Jeroen,
Replying to [comment:53 jdemeyer]:
> Why do you think that the current implementation is a "half
> measure"? I would say it fits your "super optimized standalone
> iterators with bare bone API" (except that it's currently not yet
> super optimized, see #18055 and #18056).
Yes, I am very happy with the Cython iterator (and its upcoming
optimizations) and the Parent enumerated sets (`IntegerLists*`). What
I am wondering about are the intermediate classes
(`IntegerLists*Impl`). What's their precise role? Do we really need
them?
- Are there situations where an iterator is not enough (we really need
to model the enumerated set itself), yet we can't afford the
overhead of having a Parent?
And / or
- Are the *Impl just utility classes that are mandatory to construct
the iterator?
Maybe we should have a short video conference at some point; it would
be much easier to discuss!
--
Ticket URL: <http://trac.sagemath.org/ticket/18109#comment:54>
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.
