#18346: Easier handling of vertex labels in graph backends
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.7
enhancement | Resolution:
Priority: major | Merged in:
Component: graph | Reviewers:
theory | Work issues:
Keywords: | Commit:
Authors: | d921cd9b951e14dcf7085788a254b213d3c40dfd
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
public/18346 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by ncohen):
Yo !
> That's a possibility, but it is not clear what should be the signature
of the function. What if it fails?
`LONG_MAX` ?
> It is not only that: calling directyl `mpz_get_si` or `PyInt_AS_LONG` is
faster than the cast which does call `PyInt_AsLong`. But that's true that
I do not like this `try/except`.
Well, if you can turn it into an independent function in some other module
(something integer-related) then no problem. This code is much more in
need of clarity than nanoseconds at the moment `:-P`
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18346#comment:16>
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.
