-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8351260: java.lang.AssertionError: Unexpected type tree: (ERROR) = (ERROR) #27065
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
|
@lahodaj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 62 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
vicente-romero-oracle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
/integrate |
|
Going to push as commit f9dc640.
Your commit was automatically rebased without conflicts. |
Consider a very broken declaration like this:
after seeing
@AlphaChars, javac will try to parse<@StringLength(int value = 5)String>as a type, and assign the annotation to the type. But, the text does not parse as a type well (partly due to theint value = 5), and the parsing will proceed in an expression mode. Then a search for target type is performed to attach the annotation, and that fails, as the expression tree is not expected to be part of the type.The main proposal here is to wrap the badly parsed type in an
Erroneoustree. The overall error recovery then seems to handle the situation well.The situation produces quite a few error reports, but it is not clear if this situation (esp. the nested
int value = 5) is common enough to stretch the parsing error recovery capabilities to accommodate this code.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27065/head:pull/27065$ git checkout pull/27065Update a local copy of the PR:
$ git checkout pull/27065$ git pull https://git.openjdk.org/jdk.git pull/27065/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27065View PR using the GUI difftool:
$ git pr show -t 27065Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27065.diff
Using Webrev
Link to Webrev Comment