#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 jdemeyer):
Replying to [comment:20 vbraun]:
> Usually, you see `long` because
> * the author mistakenly believes that it is the longest int type
> * the author mistakenly believes that it can hold a pointer
> * the author mistakenly believes that it is at least 64-bit
> * the author mistakenly believes that it is 64-bit on a 64-bit machine
> * cargo cult, i.e., to match legacy code
I can play that game too:
Usually, you see `int_fastN_t` because
* the author mistakenly believes that his code will never need more than N
bits (think "640K should be enough for everybody")
* the author mistakenly believes that `int_fastN_t` will yield the fastest
possible code (not true if the code is memory-bound)
> 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.
--
Ticket URL: <http://trac.sagemath.org/ticket/19337#comment:21>
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.
