rust-lang / rust-lang/rust-analyzer
Clippy lints don't show up in nested crates
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version:
tested on rust-analyzer 1.92.0 (ded5c06 2025-12-08) and rust-analyzer 0.3.2753-standalone
rustc version:
rustc 1.92.0 (ded5c06cf 2025-12-08)
editor or extension:
Helix (Arch Linux; tested both extra/helix and aur/helix-git)
relevant settings:
in ~/.config/helix/languages.toml:
[language-server.rust-analyzer.config]
check.command = "clippy"
steps to reproduce:
Set up crates:
$ cargo new meow
$ cd meow
$ cargo new --lib woof
$ cd woof
Edit (woof/)src/lib.rs to trigger a clippy lint. For example, inserting the line let _ = 'a'..'z'; into the example function causes a lint with default clippy settings.
expected behavior:
The clippy lint should show up in the editor, as it does in non-nested crates (e.g. meow in the example)
actual behavior:
No clippy lints show up in the editor
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
Reproduce the issue with the nested woof crate, Helix, and check.command = "clippy" in languages.toml; use src/lib.rs to trigger the example lint. Compare diagnostics for the nested crate with the working top-level meow crate, and consider the issue done when the clippy lint appears in the editor for woof as well.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100