-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8267321: Use switch expression for VarHandle$AccessMode lookup #4102
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 redestad! A progress list of the required criteria for merging this PR into |
JornVernee
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. I assume existing tests verify that all values of the enum are covered by the switch?
|
@cl4es 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 30 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 |
Thanks! Yes, the method with the switch is called when linking a VH, and the tests should be exhaustive in that regard. |
|
/integrate |
|
@cl4es Since your change was applied there have been 30 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 9760dba. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Using a switch expression instead of a (read-only) static
HashMapreduces initialization overhead ofVarHandle$AccessMode. This gets loaded earlier after JDK-8265079, so it started showing up in a few lambda startup tests.This also obsoletes a jtreg test that only verified that this map was optimally sized.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4102/head:pull/4102$ git checkout pull/4102Update a local copy of the PR:
$ git checkout pull/4102$ git pull https://git.openjdk.java.net/jdk pull/4102/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4102View PR using the GUI difftool:
$ git pr show -t 4102Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4102.diff