-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8354121: Use a record class rather than a lambda in AbstractMemorySegmentImpl::cleanupAction #24514
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 pminborg! A progress list of the required criteria for merging this PR into |
|
@minborg 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 8 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 |
Webrevs
|
src/java.base/share/classes/jdk/internal/foreign/AbstractMemorySegmentImpl.java
Outdated
Show resolved
Hide resolved
|
@minborg Can we just use a local record to avoid accidental local captures (which caused the issue fixed by JDK-8347407) |
liach
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.
Thanks for this error-proof improvement. Remember to update the JBS issue and PR titles.
|
/integrate |
|
Going to push as commit c3e0439.
Your commit was automatically rebased without conflicts. |
This PR proposes to use an anonymous class rather than a lambda in order to improve startup time.
We need to make sure the regression is fixed by this. It might be the case that the regression is there because JDK-8347047 actually fixed an issue so that the segments could be collected by the GC.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24514/head:pull/24514$ git checkout pull/24514Update a local copy of the PR:
$ git checkout pull/24514$ git pull https://git.openjdk.org/jdk.git pull/24514/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24514View PR using the GUI difftool:
$ git pr show -t 24514Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24514.diff
Using Webrev
Link to Webrev Comment