-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8324636: Serial: Remove Generation::block_is_obj #17555
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
|
@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 14 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.
Please ensure that the header file documentation isn't lost because of this change. Looks fine otherwise.
The doc is in |
It would be good to have documentation in the header file of the highest supertype that exposes the API, rather than having to look at the callers of that API and their API documentation to impute that information. That said, I'll leave it up to you to decide if that is sufficiently persuasive to replicate the documentation and make it more maintainable. Reviewed! |
I agree with @ysramakrishna that it would be good to retain the documentation. These name are somewhat obscure, and without prior knowledge it is hard go guess what the contract is. |
Moved the doc to the method in subclasses. |
Thanks for review. /integrate |
Going to push as commit e709842.
Your commit was automatically rebased without conflicts. |
@albertnetymk Pushed as commit e709842. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Trivial moving a method from
Generation
to subclass.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17555/head:pull/17555
$ git checkout pull/17555
Update a local copy of the PR:
$ git checkout pull/17555
$ git pull https://git.openjdk.org/jdk.git pull/17555/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17555
View PR using the GUI difftool:
$ git pr show -t 17555
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17555.diff
Webrev
Link to Webrev Comment