#15035: removing redundant set/iter conversions in graph backend
--------------------------------+-----------------------------
Reporter: slani | Owner:
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-5.12
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Dependencies:
Stopgaps: |
--------------------------------+-----------------------------
Changes (by ncohen):
* status: new => needs_review
* type: PLEASE CHANGE => enhancement
Comment:
Well `O_O`
I was worried that removing this "iter(set(" would create problems with
multiple edges, but the code from sparse_graph already avoids that...
`:-P`
I would say "good to go", while crossing my fingers with the hope that no
code which is not doctested will be reported as broken in a couple of
weeks `:-P`
Did you run the tests on the whole Sage library ? Some guys create weird
graphs outside of the graph/ folder, and there may be changes to make
there too.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/15035#comment:2>
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/groups/opt_out.
