-
-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
graph_plot: sort by id #22375
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
New commits:
|
comment:3
I don't get the point of this ticket. There are so many places where |
comment:4
Replying to @jdemeyer:
I don't really remember. But looking at the commit, it looks like this code wants to consider edges (u,v) with u ≤ v in the order in which the vertices are looped over. Sorting them by id is an easy way to avoid doing true comparisons without making deeper changes... |
comment:6
Replying to @mezzarobba:
So you're asking to review a ticket when even the ticket author cannot remember the purpose of that ticket? |
comment:7
Replying to @jdemeyer:
I do remember that the goal was to fix problems that arose when trying to disable comparisons between objects with incompatible parents (#22029)—as you know, since it was you who wanted to make this a separate ticket. I don't remember exactly why I thought this would be a correct fix here but not elsewhere. And I'm hoping for comments from people who know this code better than I do, hence the |
comment:8
As long as you don't expect me to review it :-) |
comment:9
does not apply |
comment:10
Any objections to closing this as "wontfix"? |
comment:11
no objection from me |
Avoid using comparison (which may not always work, may not provide a total order, etc.) when all we want as far (as I understand) is an arbitrary total order.
CC: @mezzarobba
Component: graph theory
Author: Marc Mezzarobba
Branch/Commit: u/jdemeyer/graph_plot__sort_by_id @
983e660
Issue created by migration from https://trac.sagemath.org/ticket/22375
The text was updated successfully, but these errors were encountered: