rust-lang / rust-lang/rust-analyzer

Analyzing works when editing comments?

Open
#13,315 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-support
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

rust-analyzer version:v0.3.1221 (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)

rustc version:rustc 1.64.0 (a55dd71d5 2022-09-19) (eg. output of rustc -V)

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTUP_HOME or CARGO_HOME)

Hi, When editing comments the Problems pane refreshes, what is it analyzing? Is it necessary? Can I turn it off?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Problems pane refresh while editing comments in VSCode and review the relevant client settings. Use the rust-analyzer: Show RA Version command to confirm the reported environment. Done should establish what is being analyzed, whether the refresh is expected, and whether it can be disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, vscode
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.