-
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
8318324: Drop redundant default methods from FFM API #16224
Conversation
👋 Welcome back mcimadamore! A progress list of the required criteria for merging this PR into |
@mcimadamore 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. |
@@ -140,4 +150,72 @@ private static long requirePowerOfTwoAndGreaterOrEqualToOne(long value) { | |||
return value; | |||
} | |||
|
|||
public long scale(long offset, long index) { |
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.
Could you add @Override
to these as well? I think it makes it clearer that these methods might be accessed through a super type.
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.
Would be nice - but note that AbstractLayoutImpl
does not extend MemoryLayout
.
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.
Ah, right...
import java.util.Objects; | ||
import java.util.Optional; | ||
import java.util.Set; | ||
import java.util.function.Function; |
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.
There are quite a few new imports here. Is it possible some imports in MemoryLayout
are now unused?
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.
No unused import here - these are just the imports required for the overrides to compile successfully.
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 mean in MemoryLayout
from which these overrides were moved.
Webrevs
|
@mcimadamore 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 31 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 15acf4b.
Your commit was automatically rebased without conflicts. |
@mcimadamore Pushed as commit 15acf4b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This PR moves turns default methods in
MemorySegment
andMemoryLayout
into ordinary abstract methods.These interfaces cannot be subclasses by developers (they are sealed), so there is no reson for having default methods there. Also, default methods can have some detrimental effects, as they cause the interfaces to be initialized more eagerly.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16224/head:pull/16224
$ git checkout pull/16224
Update a local copy of the PR:
$ git checkout pull/16224
$ git pull https://git.openjdk.org/jdk.git pull/16224/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16224
View PR using the GUI difftool:
$ git pr show -t 16224
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16224.diff
Webrev
Link to Webrev Comment