rust-lang / rust-lang/rust-clippy
Workspace-level lints
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Description
https://reviews.llvm.org/D124447
clang-tidy introduces infrastructure to create project-level diagnostics. They write a summary file per source file. In the diagnostic phase, they read all the summaries.
- You could tell me which crate in my workspace is of the lowest quality.
- With a global-view you could find new diagnostics that you cannot find with a local view
- get creative
Version
No response
Additional Labels
No response
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 reading the linked LLVM review, https://reviews.llvm.org/D124447, to understand the project-level diagnostic infrastructure and its summary files. Define a concrete workspace-level lint use case and an observable completion criterion before selecting the relevant Clippy entry points and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100