8381965: NullPointerException in TypeAnnotationPositions#30679
Open
lahodaj wants to merge 2 commits intoopenjdk:masterfrom
Open
8381965: NullPointerException in TypeAnnotationPositions#30679lahodaj wants to merge 2 commits intoopenjdk:masterfrom
lahodaj wants to merge 2 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
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.
Consider code like this:
There's an explicit lambda here,
(List<@TypeAnno String> arg) -> {}. javac will create a helper block for it in DeferredAttr.attribSpeculativeLambda:and will then speculative-attribute this block. But, when the parameters are placed into the block, they are still marked/flagged as parameters. And since the fix for https://bugs.openjdk.org/browse/JDK-8371155, the type annotations positions on the local variable type get resolved earlier in the pipeline, and even during the speculative attribution. But when the position for the type annotation is being resolved during this speculative attribution, the variable is interpreted as a parameter, but there's no (meaningful) enclosing lambda. So javac either fails with an exception, or assigns nonsensical position to the type annotation.
The primary proposal in the PR is to avoid resolving type annotations while doing speculative attribution.
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/30679/head:pull/30679$ git checkout pull/30679Update a local copy of the PR:
$ git checkout pull/30679$ git pull https://git.openjdk.org/jdk.git pull/30679/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 30679View PR using the GUI difftool:
$ git pr show -t 30679Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/30679.diff
Using Webrev
Link to Webrev Comment