rust-lang / rust-lang/rust-analyzer
check output not showing up in `problems` when `rust-analyzer.rust.analyzerTargetDir` is set
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: 0.3.1799-standalone (af4010184 2024-01-07)
Krustc version: rustc 1.75.0 (82e1608df 2023-12-21)
relevant settings: "rust-analyzer.rust.analyzerTargetDir": "target/rust-analyzer",
When the target dir is set, none of the issues show up, for example if I set my main.rs to be
fn main(){
let foo = 3;
}
cargo check will warn about the unused var, and if I unset analyzerTargetDir it shows up in Problems in vscode, but if I set it, it doesn't show up
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 in a Rust project with main.rs and rust-analyzer.rust.analyzerTargetDir set to target/rust-analyzer. Compare the unused-variable diagnostic from cargo check in VS Code with the setting enabled and disabled. Done means the diagnostic appears in the Problems view in both configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100