-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
JDK-8302202: Incorrect desugaring of null-allowed nested patterns #12572
Conversation
👋 Welcome back jlahoda! 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 sensible
@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 89 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 |
After running some more examples, the patch looks good to me too 💯 |
/integrate |
Going to push as commit dc55a7f.
Your commit was automatically rebased without conflicts. |
Considering code like:
javac will try to factor-out the common prefix, i.e.
R1
, and produce something along these lines:The problem with this code is that both cases in the nested switch must match
null
, but the bootstrap protocol only allows one case to matchnull
(theSwitchBootstraps.typeSwitch
method will return-1
fornull
). So this translation is broken, and will not match the first case if the component isnull
.There are multiple ways to solve this problem, but the proposal here is change the way we accumulate the cases from which we factor out the common prefix, by stopping the accumulation after the first nullable case.
Another related issue is that when factoring out the common prefix, if the last case in the nested switch is has an unconditional pattern, but also has a guard, we need to generate a default to continue properly in the outer switch. Currently, the default is not generated when there's an unconditional pattern in the case, despite having a guard, and hence the case as a whole is not unconditional.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12572/head:pull/12572
$ git checkout pull/12572
Update a local copy of the PR:
$ git checkout pull/12572
$ git pull https://git.openjdk.org/jdk pull/12572/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12572
View PR using the GUI difftool:
$ git pr show -t 12572
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12572.diff