-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8346610: Make all imports consistent in the FFM API #22827
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 106 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
|
import java.util.Objects; | ||
import java.util.Optional; | ||
import java.util.List; | ||
|
||
import jdk.internal.foreign.FunctionDescriptorImpl; |
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.
Just curious where this style/convention is coming from, I've always put internal packages after the import of standard APIs.
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.
Both alternatives were present and I picked the most prevailing one in the package. Also, this is what you get when you auto format in IntelliJ. But if there is a preference for the other way, we could switch. No problem.
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 don't have any strong opinion on the topic, I was mostly just curious when I saw "conformant" in the title.
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've renamed the title: "conformant" -> "consistent"
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.
copyrights should say 2025
Do we have a sense on how easy would it be, moving forward, to preserve the "correct" order of imports? E.g. if I add a new one using IntelliJ autocompletion, where would it end up? Has this patch been generated using the IDE's own import reorganization? Perhaps doing something like that might be preferrable/more maintainable longer term? |
I believe all the changes were made and committed in 2024. So, shouldn't the copyright year be 2024 then? |
The updates in this PR were generated automatically by selecting the relevant packages and then using IntelliJ's automatic Code->Optimize Imports. It is possible to tell IntelliJ to make this automatically upon saving a file: https://www.jetbrains.com/help/idea/creating-and-optimizing-imports.html#optimize-on-save |
I've typically used the year of when things are integrated. It's a bit of a gray area and I'm not super sure. Note that Skara will take your commits and squash them into a new commit which will feature a 2025 date (I think). |
I like auto import, it's great feature to ensure consistency. But the prerequisite is to have consistent settings in coding style(, and different IDEs would be different as well. https://www.jetbrains.com/help/idea/code-style-java.html#imports_table Just curious, do we have a standard IntelliJ setting for OpenJDK coding style, perhaps it's prepared by |
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. Did you also do a pass on microbenchmarks and tests? Or will that be a separate effort (probably better) ?
|
/integrate |
Going to push as commit d4e5ec2.
Your commit was automatically rebased without conflicts. |
This PR proposes to clean up all the imports in the FFM lib (excluding tests).
Passes tier1-tier3
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22827/head:pull/22827
$ git checkout pull/22827
Update a local copy of the PR:
$ git checkout pull/22827
$ git pull https://git.openjdk.org/jdk.git pull/22827/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22827
View PR using the GUI difftool:
$ git pr show -t 22827
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22827.diff
Using Webrev
Link to Webrev Comment