Skip to content

Conversation

@lahodaj
Copy link
Contributor

@lahodaj lahodaj commented Sep 3, 2025

Consider a very broken declaration like this:

void test(List<@AlphaChars <@StringLength(int value = 5)String> s){ 

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 the int 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 Erroneous tree. 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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8351260: java.lang.AssertionError: Unexpected type tree: (ERROR) = (ERROR) (Bug - P3)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27065/head:pull/27065
$ git checkout pull/27065

Update a local copy of the PR:
$ git checkout pull/27065
$ git pull https://git.openjdk.org/jdk.git pull/27065/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27065

View PR using the GUI difftool:
$ git pr show -t 27065

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27065.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 3, 2025

👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Sep 3, 2025

@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:

8351260: java.lang.AssertionError: Unexpected type tree: (ERROR) = (ERROR)

Reviewed-by: vromero

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 master branch:

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 master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Sep 3, 2025

@lahodaj The following label will be automatically applied to this pull request:

  • compiler

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added compiler compiler-dev@openjdk.org rfr Pull request is ready for review labels Sep 3, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 3, 2025

Webrevs

Copy link
Contributor

@vicente-romero-oracle vicente-romero-oracle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Sep 4, 2025
@lahodaj
Copy link
Contributor Author

lahodaj commented Sep 8, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Sep 8, 2025

Going to push as commit f9dc640.
Since your change was applied there have been 88 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Sep 8, 2025
@openjdk openjdk bot closed this Sep 8, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Sep 8, 2025
@openjdk
Copy link

openjdk bot commented Sep 8, 2025

@lahodaj Pushed as commit f9dc640.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

compiler compiler-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants