#17437: integer arrays
-------------------------------------+-------------------------------------
Reporter: amri | Owner: amri
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.5
Component: combinatorics | Resolution:
Keywords: integer arrays | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/amri/integer_arrays | c8d93b37bcc758ee840a3ae26ba47de0ff8a5796
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:7 nbruin]:
> OK, so that sounds like it should be a wrapper to provide combinatorial
methods and interfacing with parent and category infrastructure (if it's
worth the overhead). The underlying datastructure should probably be a
numpy.array, though, rather than a tuple of integer arrays.
+1.
You could still do all the combinatorial stuff using `numpy` arrays (or
something else) under the hood.
I think there are too many of these "reinvent-the-wheel" classes in Sage
(You mention `IntegerMatrix`, which is probably a good example).
--
Ticket URL: <http://trac.sagemath.org/ticket/17437#comment:8>
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.
