-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8284640: CollectorImpl class could be a record class #8179
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
Hi @altrisi, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user altrisi" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
/signed |
Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
@stuart-marks Mind review this simple cleanup? |
@altrisi 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! |
Hi, is this small PR missing anything in order to be reviewed? Thanks! |
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.
@altrisi 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 1099 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 (@phohensee, @RogerRiggs) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thanks for the review! |
I believe we need another reviewer (doesn't have to be a capital-Reviewer). I'll sponsor after that. |
/sponsor |
Going to push as commit af00880.
Your commit was automatically rebased without conflicts. |
@phohensee @altrisi Pushed as commit af00880. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi @RogerRiggs, Thanks for reviewing this PR. I have a more general question. Do we have any recommendations about using new language features in the core libraries? Thanks, |
For some new features, its an obvious yes, though personally, it should add some value to the code, not just churn the code base to be up-to-date. Also, there is quite a bit of core code that is sensitive to bootstrap and startup performance regressions. Using preview features can also be a mixed bag. The dependencies and warnings about using preview features can break the build and they are not always such an improvement to suppress the warnings and have to come back later to remove or redo the code. Some parts of the system (like javac) have to be compiled with the previous JDK, so no new features. Use new feature judiciously, meaning think broadly about the impact across the code base, not just a bit of code here and there. |
I see this one languished quite a while without a review. Sorry about that; for the uninteresting, maybe it really is insufficiently interesting to even pursue except as a starter issue. |
I assumed it was a starter issue in order to learn the patch process. |
Changes the definition of
CollectorImpl
to be a record.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/8179/head:pull/8179
$ git checkout pull/8179
Update a local copy of the PR:
$ git checkout pull/8179
$ git pull https://git.openjdk.org/jdk pull/8179/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8179
View PR using the GUI difftool:
$ git pr show -t 8179
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/8179.diff