8359383: Incorrect starting positions for implicitly typed variables #25786
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.
This fixes starting position bugs relating to implicitly typed variables; see the linked issue for details.
This also makes it possible to recover the declaration type (explicit, implicit, or
var
) from aJCVariableDecl
and, in the case ofvar
declarations, the starting position of thevar
; previously this wasn't possible.Finally, as a minor drive-by improvement, we can now pretty print
var
asvar
instead of/*missing*/
.Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25786/head:pull/25786
$ git checkout pull/25786
Update a local copy of the PR:
$ git checkout pull/25786
$ git pull https://git.openjdk.org/jdk.git pull/25786/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25786
View PR using the GUI difftool:
$ git pr show -t 25786
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25786.diff
Using Webrev
Link to Webrev Comment