rust-lang / rust-lang/rustc-dev-guide
advice for debugging incremental compilation hashing failures etc
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
Over in https://github.com/rust-lang/rust/issues/47935, @michaelwoerister wrote:
The [dependency tracking] readme is largely outdated. The "Testing the dependency graph" and "Debugging the dependency graph" sections are still correct, I think, but the rest is probably just confusing at this point.
I think we ought o move some of those sections over, and/or add some new material on how to debug incremental compilation failures. This is always something I have to kind of rediscover.
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 with the dependency tracking README and compare its sections with the current incremental compilation workflow described in rust-lang/rust issue 47935. Review the “Testing the dependency graph” and “Debugging the dependency graph” sections, then determine which remaining material needs moving, updating, or replacing. Done means the README gives maintainers practical guidance for debugging incremental compilation hashing failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100