-
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
8319556: Harmonize interface formatting in the FFM API #16528
Conversation
👋 Welcome back pminborg! A progress list of the required criteria for merging this PR into |
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.
I will prefer to see this done on a by-need basis. E.g. if the line fits in the 100 char margin, (as it seems the case in a lot of the changes here), I don't see an immediate need to make changes?
There seems to be still changes that are not needed. E.g. |
Hrmm. I reformatted all classes of the same category where at least one of them needed reformatting to make it more consistent. For example:
I am happy to do either. |
I'm fine with value layout nested classes, but what about AddressLayout/GroupLayout? |
@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 22 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 |
/integrate |
Going to push as commit 73c5f60.
Your commit was automatically rebased without conflicts. |
This PR proposes to remove two
permits
declarations where the line overflows the stipulated maximum column with. Also, it proposes to harmonize the layout ofpermit
formatting so they are the the same throughout the API.This PR might be perceived as over worked but I think it nice to get consistency across the API now that we go final.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16528/head:pull/16528
$ git checkout pull/16528
Update a local copy of the PR:
$ git checkout pull/16528
$ git pull https://git.openjdk.org/jdk.git pull/16528/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16528
View PR using the GUI difftool:
$ git pr show -t 16528
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16528.diff
Webrev
Link to Webrev Comment