JuliaGraphs / JuliaGraphs/Graphs.jl
Interface without needing `AbstractGraph`?
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 538
- Forks
- 128
- Avg merge
- 10h 25m
- Merged PRs (30d)
- 2
Description
In https://juliagraphs.org/Graphs.jl/stable/ecosystem/interface/ it specifies that we need to subtype to AbstractGraph to use these methods. I am wondering if there could be a trait-based version instead? Since Julia doesn't allow multiple inheritance it means we wouldn't be able to depend on both our own abstract type (which includes non-graph objects) as well as interface with Graphs.jl
cc @robdancer. x-ref https://github.com/SymbolicML/DynamicExpressions.jl/pull/98#issuecomment-2284986304
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 with the ecosystem interface documentation at https://juliagraphs.org/Graphs.jl/stable/ecosystem/interface/ and review how requiring AbstractGraph constrains users with their own abstract types. Define what a trait-based interface would need to support, then document the agreed design and its compatibility with existing Graphs.jl methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100