-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8309054: Parsing of erroneous patterns succeeds #14205
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 abimpoudis! A progress list of the required criteria for merging this PR into |
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.
Looks good to me.
@biboudis 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 10 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@lahodaj) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
Going to push as commit 4f3a95a.
Your commit was automatically rebased without conflicts. |
Moving the logic of type test pattern detection from
parsePattern
tovariableDeclaratorRest
in #13528 made the logic of the latter too complex. The regression in this JBS would be fixed by introducing two additional if-guards (e.g.,if (!typePattern)
); conditional on whether we are detecting a local variable or a type pattern. This PR removes this.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14205/head:pull/14205
$ git checkout pull/14205
Update a local copy of the PR:
$ git checkout pull/14205
$ git pull https://git.openjdk.org/jdk.git pull/14205/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14205
View PR using the GUI difftool:
$ git pr show -t 14205
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14205.diff
Webrev
Link to Webrev Comment