JuliaGraphs / JuliaGraphs/GraphProperties.jl
split into multiple packages
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The goal of enumerating each well-known graph property and family conflicts with the goal of being a light-weight dependency. Even though this package does not have almost any executable code, defining a great number of new types could still be taxing on the compiler, I guess.
It might make sense to:
-
Split up the abstract supertype from the definitions of particular properties. Then loading the abstract supertype would not imply loading all the properties.
-
Split up some of the particular property definitions from some of the others. Then loading a single concrete property would not imply loading all properties.
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 reviewing the package entry points and the definitions of the abstract supertype and concrete graph properties. Determine module boundaries that prevent loading every property when only the abstract type or one concrete property is needed. Done means the package is split into independently loadable groups without changing the property definitions' behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100