rust-lang / rust-lang/rust-analyzer
rust-analyzer is confused by slint's codegen and macros, and takes too long to update
Open
Nobody has claimed this yet.
A-macro
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Hi,
When using Visual Studio Code with and Slint, quite often rust-analyzer struggles with expanding the macros and with the codegen as well, while RustRover seems to be able to keep up with those accurately.
By struggle, I mean:
- taking a lot of time to provide the completion
- not being able to offer completion at all
- missed invalidation after codegen
Cheers,
Alex
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
Start by reproducing the issue in Visual Studio Code with Slint, focusing on macro and codegen expansion, completion delays or failures, and missed invalidation after codegen. The issue does not name files, tests, or an entry point; done means completion is timely and accurate and updates correctly after code generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100