Graphs.jl 2.0 #258
Closed
Graphs.jl 2.0 #258
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 110545f.
|
Todo: migrate this to GraphsBase.jl |
|
@etiennedeg do you need help for the transfer to GraphsBase? happy to lend a hand |
|
Sorry, I should have done it earlier, I will try to do it quickly (probably not today, but I should find some time tomorrow) |
|
No rush, I was just checking in! Got a CS sudent intern starting on September 19th who will give us a hand on this behemoth of a project ;) |
|
Closing in favor of JuliaGraphs/GraphsBase.jl#9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is a first draft for the Graphs 2.0, in order to get something actionable.
For the moment, there is not much in it: the implementation of major parts of the new interface, new interface applied to SimpleGraphs, and a rewriting of
a_starfollowing the new interface to test it a little bit. I haven't tested anything for the moment.In order to keep the discussion on the new API focused in one place, I will detail my thoughts and observations about the new interface and its practicalities in the API 2.0 discussion , see this comment for some details on this draft.