rust-lang / rust-lang/rust-analyzer
configure rust-analyzer lints with Cargo `[lints]` table
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
I'm running into some rust-analyzer lints in my code that I'd like to disable on the project as a whole.
Rust 1.74 stabilized the [lints] & [workspace.lints] tables for Cargo.toml. It is already possible to configure lints for clippy & rustc here, and it seems like an appropriate place to configure rust-analyzer lints as well
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 Cargo.toml's [lints] and [workspace.lints] documentation and comparing it with rust-analyzer's current lint configuration behavior. Define how project- and workspace-level rust-analyzer lint settings should be represented, and verify that they can disable selected rust-analyzer lints without changing existing rustc or Clippy configuration.
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
- Mostly clear
- Newbie friendliness
- 35/100