JuliaGraphs / JuliaGraphs/Graphs.jl
Split out a GraphsBase package?
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 538
- Forks
- 128
- Avg merge
- 10h 25m
- Merged PRs (30d)
- 2
Description
Graphs.jl is not an heavy packgage, but still it adds 1 or 2 secs to the latency of packages depending on it (my use case is GraphNeuralNetworks.jl).
There would be some interest in moving the function definitions needed to define a custom graph type
https://juliagraphs.org/Graphs.jl/dev/ecosystem/interface/
and possibly a few more to a separate lean package (similarly to what StatsBase.jl, DataAPI.jl, ChainRulesCore.jl do)?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Graphs.jl ecosystem interface at the linked documentation, focusing on the functions needed for custom graph types. Compare the package boundaries and dependency roles of StatsBase.jl, DataAPI.jl, and ChainRulesCore.jl, then assess which definitions could form a lean package and how GraphNeuralNetworks.jl would depend on it. Done means an agreed package scope and migration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100