rust-lang / rust-lang/rust-analyzer
Autocompletion suggests private libstd items
Open
Nobody has claimed this yet.
A-completion
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: 0.3.2658-standalone
rustc version: rustc 1.89.0 (29483883e 2025-08-04)
editor or extension: VS Code
code snippet to reproduce:
fn main() {
env::var
}
Notably, the actual env::var item isn't even suggested at all.
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 completion behavior from the provided Rust snippet in VS Code using the reported rust-analyzer and rustc versions. Investigate the completion path for env::var and the private libstd items shown in the screenshot. Done means the public env::var item is suggested and private library items are not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100