-
**rust-analyzer version**: 0.3.2129-standalone
**rustc version**: rustc 1.81.0 (eeb90cda1 2024-09-04)
**editor or extension**: VSCode
**relevant settings**: Default
**repository link (if public,…
-
Hello hello :)
Due to organizational reasons we usually have the code under audit as part of a larger repository which also contains our organizational stuff.
VSCode's language servers tend to beh…
-
**rust-analyzer version**: rust-analyzer version: 0.3.1932-standalone (47a901b9b 2024-04-21)
**rustc version**: 1.77.2
**editor or extension**: VSCode Insiders with RA 0.3.1932
It's pretty co…
-
- [ ] Migrate to rustc_smir for API stability between different versions of rust compilers.
- [x] Support updated versions of Rust compilers.
- [ ] More complete documents on how lockbud works and ho…
-
Hello.
I've been encountering this specific problem with "Rust-Analyzer: Debug" no matter what platform I am on. I've been able to replicate this on Windows, and Mac OS. Now I'm on Arch Linux and af…
-
### Description
From time to time I notice that there are a bunch of ruby processes where I'm pretty sure they are related to ruby-lsp even if the Rails project got already closed or VS Code is no lo…
-
some projects need to use rustc-related dependency (like rust-lang/clippy)
but RustRover cannot find them
I have two choices:
1. do nothing. can compile
2. add
` rustc_xxx = {path = ".../rust/co…
-
When working for a while in a large codebase, I get a lot of errors like this one from `tracing::info!` macro invocations:
> non-primitive cast: `&Arguments` as `&dyn Value`
This seems to come f…
-
Using Rust-Analyzer inside VS Code.
Add ```image = "0.24"``` to dependencies = works fine.
Add ```image = "0.25.2"``` to dependencies leads to Rust-Analyzer errors:
```
Failed to run build s…
-
When `"rust-analyzer.completion.callable.snippets": "fill_arguments"` is set, r-a completes the parens for function calls flawlessly in most situations. But when inside a match arm, if I only typed …