rust-lang / rust-lang/rust-clippy
check if we can get a rustc with debug assertions on CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
There have been cases recently where clippy would crash if rustc was build with debug-assertions enabled.
https://github.com/rust-lang/rust-clippy/issues/3628
https://github.com/rust-lang/rust/issues/57298
To earlier catch regressions it might be helpful if we could get something like a rustc master tarball that has debug assertions enabled but I'm not sure if this exists.
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 by reviewing the two linked Rust and Clippy issues, then inspect the repository's existing CI configuration. Determine whether a rustc master tarball with debug assertions is available and whether CI could use it. Done means a concrete, maintainable CI approach is identified and its coverage of debug-assertion regressions is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100