#19337: Improve asteroidal triples code
-------------------------------------+-------------------------------------
Reporter: dcoudert | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.9
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: David Coudert | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dcoudert/asteroid | e32015d13649c7df56362fc9fd2b57937f465705
Dependencies: #19334 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
Replying to [comment:21 jdemeyer]:
> > what is the minimum bit-width required
> I don't think that one ''should'' always answer this question. There are
valid use cases for types which have different sizes on 32-bit and 64-bit
systems.
I agree that there are valid use cases, but
* int/long are also terrible for that; They encode mostly encode
historical accidents, e.g. long is different on 64-bit linux vs 64-bit
windows on the same hardware
* in Mathematics, correctness and reproducibility (including on different
OS/hardware) are much more important than elsewhere. If you can't trust
that the result is correct then neither speed nor memory usage matters.
--
Ticket URL: <http://trac.sagemath.org/ticket/19337#comment:23>
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.
