rust-lang / rust-lang/rust-analyzer
Document symbols are not available until the document is changed
Open
Nobody has claimed this yet.
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Hi!
- Trigger the
textDocument/documentSymbolrequest from VS Code (egCmd-Shift-O) after a fresh Rust Analyzer start/reload. * No symbols are returned (or rather, it looks like the request is not processed) - Send a
textDocument/didChangerequest (eg type a whitespce, no need to save) - Re-send the (
textDocument/documentSymbol) request - This time symbols are returned
Is this a known/expected behaviour?
rust-analyzer version: 0.3.1178-standalone (a670ff888 2022-08-21)
rustc version: rustc 1.61.0 (fe5b13d68 2022-05-18)
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 report in VS Code with Rust Analyzer after a fresh restart or reload by sending textDocument/documentSymbol before any edit, then send textDocument/didChange and retry. The issue is resolved when document symbols are returned before a document change, or the expected behavior is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100