-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8268764: Use Long.hashCode() instead of int-cast where applicable #4491
Conversation
👋 Welcome back stsypanov! A progress list of the required criteria for merging this PR into |
@stsypanov The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
The changes look good to me, we have done the same thing elsewhere. This changes things in different functional areas, which is maybe unusual, but seems fine for a small change as long as nobody objects. Some of the files also need a (C) year update. |
Hi Kevin, thanks for review! I've updated copy-right year |
OK, one more (C) in src/jdk.jdi/share/classes/com/sun/tools/jdi/ReferenceTypeImpl.java and done. 8-) |
Right, done! |
/integrate |
@stsypanov This PR has not yet been marked as ready for integration. |
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.
Speaking only to the media classes in the desktop module (you'll need approval from others for the other cases),
I can't think of any actual problem this will create, but honestly I can't see any actual value in it either.
|
@stsypanov 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 1209 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. 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 (@kevinjwalls, @prrace, @azuev-java, @mrserb) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/reviewers 3 |
@prrace |
@stsypanov This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Let's wait, bridgekeeper. |
@stsypanov This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Let's wait, bridgekeeper. |
/integrate |
@stsypanov |
/sponsor |
Going to push as commit 124f823.
Your commit was automatically rebased without conflicts. |
@mrserb @stsypanov Pushed as commit 124f823. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
In some JDK classes there's still the following hashCode() implementation:
This outdated expression should be replaced with Long.hashCode(long) as it
uses all bits of the original value, does not discard any information upfront. For example, depending on how you are generating the IDs, the upper bits could change more frequently (or the opposite).
does not introduce any bias towards values with more ones (zeros), as it would be the case if the two halves were combined with an OR (AND) operation.
See https://stackoverflow.com/a/4045083
This is related to #4309
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4491/head:pull/4491
$ git checkout pull/4491
Update a local copy of the PR:
$ git checkout pull/4491
$ git pull https://git.openjdk.java.net/jdk pull/4491/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4491
View PR using the GUI difftool:
$ git pr show -t 4491
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4491.diff