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
Unify graph backends #30769
Comments
comment:1
Note that I waited about a second between creating the graphs and timing each time. If you hit the next time too fast, I got a slowdown in each case. |
This comment has been minimized.
This comment has been minimized.
comment:3
Replying to @kliem:
I added corresponding |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Reviewer: David Coudert |
comment:7
For me this patch is good to go. Thank you. |
comment:8
Thank you for reviewing. |
Changed branch from u/gh-kliem/unify_graph_backends to |
This is a follow up to #28896.
We further unify the behavior of dense and sparse (dynamic) graph backends.
Adding and deleting edges now share common methods.
In particular,
DenseCGraph
andSparseCGraph
also behave the same in the following way now:Note that this ticket is also a step towards #28259:
Comparison:
Before:
After:
Depends on #30665
CC: @videlec @dimpase @dcoudert @slel
Component: graph theory
Keywords: graph backend
Author: Jonathan Kliem
Branch/Commit:
66b3dde
Reviewer: David Coudert
Issue created by migration from https://trac.sagemath.org/ticket/30769
The text was updated successfully, but these errors were encountered: