#16453: Cythonize quiver paths
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: algebra | Resolution:
Keywords: | Merged in:
Authors: Simon King | Reviewers:
Report Upstream: N/A | Work issues: Fix issue in bounded
Branch: | integer sequences
u/SimonKing/cythonize_quiver_paths | Commit:
Dependencies: #15820 | 73ac68974379d51ff7a4a22aed7539b480668be8
| Stopgaps:
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:60 jdemeyer]:
> I wouldn't worry about the bounds of your integers, I would guess that
fast operations are more important.
The point is that the speed of most operations depends on the bound of the
integers. And the bound of the integers depends on the encoding.
> But if you really care, you need to benchmark...
In the latest commit, I allow to choose between two implementations. The
choice happens when creating a path semigroup. Of course, having two
implementations ''in a single element class'' is not optimal. I did it in
this way in order to be able to do some benchmarks. Later, we should
either pick a single implementation once and for all, or we should provide
two distinct element classes for the two implementations.
Next, I'll try to come up with meaningful benchmarks.
--
Ticket URL: <http://trac.sagemath.org/ticket/16453#comment:62>
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.
