JuliaGraphs / JuliaGraphs/GraphsBase.jl
Which functions go where?
Open
Nobody has claimed this yet.
question
- Dominant language
- Julia
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Splitting out GraphsBase.jl means deciding which functions
- Have to be overridden by users (the "interface")
- Rely on the interface while remaining reasonably basic (the "core")
- Rely on the interface and core while adding more sophisticated functionality (the "algorithms")
The interface and core will go in GraphsBase.jl, the algorithms will remain in Graphs.jl.
Contributor guide
No contributing guide indexed for this repository
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 comparing the functions in Graphs.jl with the planned split in GraphsBase.jl. Determine which functions form the user-overridden interface, which are basic core functionality, and which are higher-level algorithms. Done means the interface and core are placed in GraphsBase.jl while algorithms remain in Graphs.jl.
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