8289558: Need spec clarification of j.l.foreign.*Layout #98
Conversation
👋 Welcome back mcimadamore! A progress list of the required criteria for merging this PR into |
@@ -155,6 +159,7 @@ public boolean equals(Object that) { | |||
} | |||
|
|||
return Objects.equals(name, ((AbstractLayout) that).name) && | |||
Objects.equals(size, ((AbstractLayout)that).size) && |
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 consolidated things a bit here - the superclass should check name, size and alignment - while subclasses should only check additional properties.
@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. |
Webrevs
|
Consolidate hashcode
@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 16 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 889150b.
Your commit was automatically rebased without conflicts. |
@mcimadamore Pushed as commit 889150b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This patch fixes few javadoc issues in the memory layout API.
The main issues are that
SequenceLayout::flatten
andSequenceLayout::reshape
still mention failures caused by a lack of size. But that condition is no longer possible in the new API.The javadoc of
ValueLayout::arrayElementVarHandle
is suboptimal and can be clarified - UOE is only thrown if the value layout alignment is bigger than its size.Finally, the
MemoryLayout::equals
method does not mention value layout carriers.The JBS issue associated with this PR mentions also other issues, mostly related to the overly broad visibility of some of the methods in the javadoc (e.g. isPadding). Unfortunately, given the presence of an intermediate, non-public, abstract class, this is what we get from javadoc. Fixing these issues would require a deeper restructuring of the implementation, which would be too riskt at this stage.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk19 pull/98/head:pull/98
$ git checkout pull/98
Update a local copy of the PR:
$ git checkout pull/98
$ git pull https://git.openjdk.org/jdk19 pull/98/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 98
View PR using the GUI difftool:
$ git pr show -t 98
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk19/pull/98.diff