Fix rust-analyzer "Go to Definition" inside #[builder] functions#385
Merged
Conversation
Veetaha
approved these changes
Jun 10, 2026
Merged
Collaborator
|
This change was released in v3.9.2 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rust-analyzer's "Go to Definition" function is currently broken when used inside a function annotated with
#[builder]because of the way it prioritizes spans.Prior to this change, using "Go to Definition" on any token within the function body led the analyzer wildly astray. After the fix, it correctly jumps to the item definition.
As far as I can tell, this change doesn't introduce any regressions or changes in generated documentation.