Typical workflow for precompilation and JET

Open
  • Is something wrong?
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia
Domain
developer-experience

Research direction

Start by identifying the package's most common graph types and reviewing the proposed PrecompileTools.jl and JET.jl workflow. Define what a typical workflow should cover and how its precompilation and runtime dispatch-analysis results will be evaluated; the issue does not name files or tests.

Written by the indexing model from the issue text.

Description

enhancement

Once this package gets off the ground, it would be nice to define a typical workflow involving the most common graph types. This would have benefits beyond mere testing:

  • allow precompilation with PrecompileTools.jl
  • allow runtime dispatch analysis with JET.jl (see this comment)
Dominant language
Julia
Stars
11
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaGraphs/GraphsBase.jl

All issues in JuliaGraphs/GraphsBase.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.