Repository navigation
Fixing completion for for-each construct without type. - #8762
Merged
Merged
Conversation
mbien
approved these changes
Sep 1, 2025
mbien
left a comment
Member
There was a problem hiding this comment.
awesome! (don't forget to squash)
lahodaj
force-pushed
the
completion-for-each-without-type
branch
from
September 2, 2025 05:04
68075ab to
ce0da80
Compare
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.
One of my pet peeves is this case with code completion:
The CC does not work here - it will simply show nothing. The reason, as far as I can tell is that the end pos for the variable is wrong.
lib.nbjavactries to correct the position, butstoreEndwon't let the position to be set beforeerrorEndPos. The main proposal here is to force-set the "correct" end position.There's also a small tweak in the CC to make the CC work for cases where there is an undefined type like:
^Add meaningful description above
Click to collapse/expand PR instructions
By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -
Please make sure (eg.
git log) that all commits have a valid name and email address for you in the Author field.If you're a first time contributor, see the Contributing guidelines for more information.
If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.
PR approval and merge checklist:
If this PR targets the delivery branch: don't merge. (full wiki article)