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
8274715: Implement forEach in Collections.CopiesList #2524
Conversation
👋 Welcome back stsypanov! A progress list of the required criteria for merging this PR into |
@stsypanov The following label 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 list. If you would like to change these labels, use the /label pull request command. |
@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! |
@stsypanov This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
/open |
@stsypanov @HostUserDetails{id=10835776, username='stsypanov', fullName='null'} this pull request is now open |
Webrevs
|
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.
Core collection classes should have optimized versions of forEach, so this is a good change in principle. Although CopiesList.forEach is unlikely to be performance critical.
I implemented many similar optimizations for core collection classes in past years.
Many of them are benchmarked in test/jdk/java/util/Collection/IteratorMicroBenchmark.java
That was written pre-JMH.
I see a JMH benchmark was written, but it is not part of the commit.
There are a number of unrelated changes in this commit that look like they were suggested by a lint-like tool. Such changes are good, but they belong in a separate cleanup commit applied across large portions of the jdk sources.
I would not use "var" here - more readable with concrete types.
Similarly, I prefer not using diamond for
return new Enumeration() {
@Martin-Buchholz thanks for review! I've reverted irrelevant changes and added the benchmark. |
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.
Thanks - TIL about Blackhole::consume .
All Java source files should end with exactly one newline. Configure your editor to make it so.
Done |
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!
|
@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 16 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 (@Martin-Buchholz) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@stsypanov |
I've never sponsored a github change and https://openjdk.java.net/sponsor/ is unhelpfully stale. /sponsor |
Going to push as commit df7b0c7.
Your commit was automatically rebased without conflicts. |
@Martin-Buchholz @stsypanov Pushed as commit df7b0c7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Originally was proposed by Zheka Kozlov here: http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-December/057192.html
Just a tiny optimization: we can use for-i loop instead of
Iterable.forEach()
which is relying on iterator.Simple benchmark demonstrates slight improvement:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/2524/head:pull/2524
$ git checkout pull/2524
Update a local copy of the PR:
$ git checkout pull/2524
$ git pull https://git.openjdk.java.net/jdk pull/2524/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2524
View PR using the GUI difftool:
$ git pr show -t 2524
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/2524.diff