rust-analyzer icon indicating copy to clipboard operation
rust-analyzer copied to clipboard

A Rust compiler front-end for IDEs

Results 654 rust-analyzer issues
Sort by recently updated
recently updated
newest added

**rust-analyzer version**: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P) rust-analyzer version: 0.3.1162-standalone (634cfe3d7 2022-08-07) **rustc version**: (eg. output of `rustc -V`) rustc 1.63.0 (4b91a6ea7...

C-bug
A-ide

Resolves #12510 This PR adds an assist, which convert 2-arm match that evaluates to a boolean into the equivalent matches! invocation.

It is not an uncommon pattern for build scripts to invoke rustc to detect whether some features are available. Popular crates like anyhow and eyre do that, and the autocfg...

Broken Window
C-bug

I always getting following language server error notifications for the `rust-analyzer`. `Request textDocument/semanticTokens/range failed.` `Request textDocument/inlayHint failed.` `Request textDocument/semanticTokens/full failed.` The Output debug print is the following. ```text Panic context:...

A-ty
S-unactionable

Closes https://github.com/rust-lang/rust-analyzer/issues/12973

I think that it would be nice to have the outline go deeper into functions and also show match arms as an entry ![image](https://user-images.githubusercontent.com/30810131/181777601-f664a002-287b-43c4-a537-3480a6d41f20.png)

Given a 2-arm match that evaluates to a boolean we should offer an assist/lint diagnostic to turn it into the equivalent `matches!` invocation. ```rs match scrutinee { Some(val) if val.cond()...

good first issue
S-actionable
A-assists
C-feature

**rust-analyzer version**: 2b472f668 2022-07-31 **rustc version**: 1.62.1 below are details: ```shell INFO [8/12/2022, 11:37:55 AM]: Extension version: 0.4.1157 INFO [8/12/2022, 11:37:55 AM]: Using configuration { cargoRunner: null, runnableEnv: null, server:...

I'm viewing this project https://github.com/bjoernQ/esp32-rust-nostd-temperature-logger in VS Code and get "environment variable not defined" over `env!` macror: ![image](https://user-images.githubusercontent.com/314607/184290817-feecd67e-8039-48f3-b4ec-d75fc44c26a2.png) I tried to define environment values via _settings.json_, but is not successful:...