rust-lang / rust-lang/rust-analyzer
Honor build.target-dir from .cargo/config.toml
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
This is a follow-up to:
- #18296
- #18827
With that PR, rust-analyzer honors the environment variable CARGO_TARGET_DIR but this is not the only location users may change the target directory.
The other option is using target-dir in the Cargo config:
https://doc.rust-lang.org/cargo/reference/config.html#buildtarget-dir
Which rust-analyzer still doesn't honor.
Due to the same reasoning it was decided R-A should honor CARGO_TARGET_DIR, i would request that this config be honored 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 tracing rust-analyzer’s existing handling of CARGO_TARGET_DIR and how it reads Cargo configuration, then compare that with Cargo’s build.target-dir setting. Done means rust-analyzer uses the configured target directory in .cargo/config.toml as well as the environment-variable path, with behavior checked against the linked follow-up context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100