-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8270282: Semantically rename reference processing subphases #4752
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 ayang! A progress list of the required criteria for merging this PR into |
|
@albertnetymk 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
|
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.
Mostly looks good, except for a naming choice.
| ~ReferenceProcessorPhaseTimes(); | ||
|
|
||
| WorkerDataArray<double>* phase2_worker_time_sec() const { return _phase2_worker_time_sec; } | ||
| WorkerDataArray<double>* SoftWeakFinalRefsPhase_worker_time_sec() const { return _SoftWeakFinalRefsPhase_worker_time_sec; } |
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.
This is a weird function name. I understand why, but I'm not convinced. We have process_soft_weak_final_refs and the like, for example.
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.
How about soft_weak_final_refs_phase_worker_time_sec()?
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.
Yes, that's normal style. It's quite a mouthful, but it's not like it gets written very often. With that change, I think this PR looks good.
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.
Agree with that.
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 after discussed function name change.
|
@albertnetymk 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 13 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 |
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 apart from that naming issue.
| ~ReferenceProcessorPhaseTimes(); | ||
|
|
||
| WorkerDataArray<double>* phase2_worker_time_sec() const { return _phase2_worker_time_sec; } | ||
| WorkerDataArray<double>* SoftWeakFinalRefsPhase_worker_time_sec() const { return _SoftWeakFinalRefsPhase_worker_time_sec; } |
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.
Agree with that.
|
Thanks for the review. /integrate |
|
Going to push as commit 565ec85.
Your commit was automatically rebased without conflicts. |
|
@albertnetymk Pushed as commit 565ec85. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Simple rename of phase{2,3,4} to something with semantic meaning.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4752/head:pull/4752$ git checkout pull/4752Update a local copy of the PR:
$ git checkout pull/4752$ git pull https://git.openjdk.java.net/jdk pull/4752/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4752View PR using the GUI difftool:
$ git pr show -t 4752Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4752.diff