-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8300237: Minor improvements in MethodHandles #12025
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 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. |
Webrevs
|
final List<Class<?>> empty = List.of(); | ||
return lists.stream().reduce((p, q) -> p.size() >= q.size() ? p : q).orElse(empty); | ||
map(MethodType::ptypes). | ||
reduce((p, q) -> p.length >= q.length ? p : q).orElse(EMPTY); |
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.
Could avoid the need to introduce EMPTY
if you make the stream expression return the longest list directly:
reduce((p, q) -> {
var longest = (p.size() >= q.size()) ? p : q;
return List.of(Arrays.copyOfRange(longest, skipSize, longest.size()); // checking isEmpty() is redundant here since we filter on `t.parameterCount() > skipSize`
}).orElse(List.of());
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.
Using lambdas inside MethodHandles is quite dangerous given that lambdas are initialized using method handles. It may work now because longuestParameterList() is not called when initializing a lambda but it may make any changes in the implementation of lambdas painfull in the future.
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.
Precious little method handle use in lambda bootstrap since JDK 11. Though I agree with the sentiment - having fixed a number of bootstrap issues in the past - MethodHandles
is a small step up the abstraction ladder and the code in particular already uses a number of method refs and lambdas.
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.
ok, two small changes,
-
formatting: usually the method call in a stream are aligned with the '.' at the beginning
stream .filter(...) .map(...)
instead of at the end.
-
the reduce is a max(),
max(Comparator.comparingInt(List::size))
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.
@forax formatting is fixed. As of max() I think we can improve this even more by hoisting max() before calling ptypes()
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.
Remove EMPTY
(using my earlier suggestion or by simply inlining new Class<?>[0]
) and I think this looks OK if framed as a code cleanup. The affected code isn't very performance sensitive as it's only used in the setup for MHs.loop
combinators, which are likely to be rare in practice.
import java.util.List; | ||
import java.util.Objects; | ||
import java.util.Set; | ||
import java.util.*; |
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.
oops
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.
Reverted
.filter(t -> t.parameterCount() > skipSize) | ||
.max(Comparator.comparing(MethodType::parameterCount)) | ||
.map(MethodType::ptypes) | ||
.map(longest -> List.of(Arrays.copyOfRange(longest, skipSize, longest.length))) |
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.
i think you can fuse these two map() calls
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.
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.
LGTM
return lists.stream().reduce((p, q) -> p.size() >= q.size() ? p : q).orElse(empty); | ||
.map(MethodHandle::type) | ||
.filter(t -> t.parameterCount() > skipSize) | ||
.max(Comparator.comparing(MethodType::parameterCount)) |
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.
@forax suggested Comparator.comparingInt
here, which may or may not help avoid some boxing.
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.
Nice point, done!
@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 214 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 (@cl4es) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Looks good to me, |
/integrate |
@stsypanov |
/sponsor |
Going to push as commit 754f6e6.
Your commit was automatically rebased without conflicts. |
@cl4es @stsypanov Pushed as commit 754f6e6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
MethodType.ptypes()
can be used instead ofMethodType.parameterList()
when we don't need a copyStream.reduce()
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12025/head:pull/12025
$ git checkout pull/12025
Update a local copy of the PR:
$ git checkout pull/12025
$ git pull https://git.openjdk.org/jdk pull/12025/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12025
View PR using the GUI difftool:
$ git pr show -t 12025
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12025.diff