rust-lang / rust-lang/rust-analyzer
Tons of incorrect typecheck errors inside miri
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: rust-analyzer version: 0.4.2973-standalone [/home/gh-bjorn3/.vscode-server/extensions/rust-lang.rust-analyzer-0.4.2973-linux-arm64/server/rust-analyzer]
rustc version: rustc 1.98.0-beta.2 (08d5b675a 2026-07-12)
editor or extension: VSCode
relevant settings: Fairly standard rust-lang/rust config
repository link (if public, optional): https://github.com/rust-lang/rust
If I open for example src/tools/miri/src/machine.rs, I'm getting several errors like expected &[OpTy<'_, CtfeProvenance>], found &Vec<OpTy<'_, Provenance>, Global> from rust-analyzer. Other files are way worse.
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 diagnostics by opening src/tools/miri/src/machine.rs in VSCode with the reported rust-analyzer and rustc versions. Start by examining the type mismatch errors and compare behavior across the other affected files. Done means rust-analyzer no longer reports the incorrect typecheck errors inside Miri.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100