#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 | 5f7a883c07534a0d7861dd4dc46e0b45ae4ff1ed
Dependencies: #18181, #18184 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by nthiery):
Replying to [comment:63 jdemeyer]:
> Replying to [comment:44 nthiery]:
> > Maybe slightly more systematic class names could
> > help; say: `IntegerLists`, `IntegerListsLex`, `IntegerListsBackend`,
> > `IntegerListsLexBackend`.
>
> Do you find `...Backend` more clear than `...Impl`? If you care a lot, I
can change it, but it smells like bike-shedding.
I have a preference for `Backend` since we use this vocable elsewhere in
Sage (e.g. in the graph library), but don't really care otherwise; you
choose. My comment was more about having a consistent naming scheme. It
could be enough to e.g. rename `IntegerListsImpl_invlex` to
`IntegerListsLexImpl`.
Thanks by the way for investigating how to better do the pickling!
--
Ticket URL: <http://trac.sagemath.org/ticket/18109#comment:65>
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.
