JDK-8235837 : Memory access API refinements
- Type: Enhancement
- Component: core-libs
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-12-12
- Updated: 2020-01-29
- Resolved: 2020-01-15
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 14 | JDK 15 |
|---|---|
14 b32Fixed  |
15Fixed |
Related Reports
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Over the course of the RFR and CSR review, several naming-related issues and other minor refinements were pointed out: * There doesn't seem to be a predicate for "can I call close without an exception?" (isAlive && isAccessible) isn't sufficient. * Should MemoryAddress implement Comparable? * should we have a way to ask a Layout if its size is specified ? * should we merge MemoryLayouts and MemoryLayout? * MemoryAddress::offset() vs. MemoryAddress::offset(long) -- not much distance between these two semantically different operations * MemorySegment::isAccessible() -- as the A* word is overloaded, some other name should be found? * MemorySegment::acquire() -- replace with MemorySegment::fork?
Comments
|