Fix position context of enum/decl literal in if/while/for#2342
Merged
Conversation
Techatrix
requested changes
Jun 5, 2025
Techatrix
left a comment
Member
There was a problem hiding this comment.
This needs to handle for and while loops as well.
Contributor
Author
|
Hm… Do you have any example code of loops that have only a decl literal as the body? I know it’s possible to have a break statement with a decl literal, but we already support that 🤔 |
Member
None that is semantically valid but that doesn't matter regarding the position context. The token sequence const foo: ?u32 = undefined;
const bar = while (foo) .<request completions here> |
if statementif/while/for
Techatrix
approved these changes
Jun 5, 2025
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
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.
For example: