#14862: Compositions accept any input
-------------------------------------+-------------------------------------
Reporter: stumpc5 | Owner: sage-combinat
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.13
Component: combinatorics | Resolution:
Keywords: composition, | Merged in:
FindStat | Reviewers:
Authors: | Work issues: provide a test in the
Report Upstream: N/A | constructor
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by nbruin):
Replying to [comment:17 darij]:
> Oops, when I said that "it" would slow things down, I meant the generic
dispatch routine (as factory or function or whatever). And I know that
this can be fixed by calling specific routines; I'm just saying it'll
probably require a patchbomb this way or another, because at the moment I
think most code that builds compositions calls {{{Composition}}}.
They won't be importing it from the global scope (they wouldn't even have
a convenient way of accessing it). The files that use `Composition` would
have a line `from sage.combinat.composition import Composition` and that
wouldn't be affected in any way. No need to patch that.
--
Ticket URL: <http://trac.sagemath.org/ticket/14862#comment:18>
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/groups/opt_out.
