LukeMathWalker / LukeMathWalker/cargo-px
Re-compute codegen plan after the execution of each code-generation step
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 63
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
There are pathological cases (see here) that might require us to re-compute the codegen plan after the execution of each code generation unit.
We could start off with a pretty naive implementation (i.e. cargo generate-lockfile + re-compute the codegen plan - the units we already generated) and then make it more sophisticated over time (e.g. detect if the newly generated manifest has added any new dependency edges and skip re-generation if that's not the case).
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 tracing the code-generation plan and the existing cargo generate-lockfile entry point. Determine how generated units are tracked and how the plan can be recomputed after each code-generation step. Done means pathological cases can add dependencies during generation without regenerating units that already completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100