- 
    Bug 
- 
    Resolution: Fixed
- 
     P3 P3
- 
    15
- 
        b29
- 
        Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8248278 | 16 | Maurizio Cimadamore | P3 | Resolved | Fixed | b04 | 
| JDK-8250090 | 15.0.2 | Maurizio Cimadamore | P3 | Resolved | Fixed | b01 | 
| JDK-8250389 | 15.0.1 | Maurizio Cimadamore | P3 | Resolved | Fixed | b03 | 
                    There are some things that need to be improved in the javadoc of the foreign memory API:
* the javadoc for close() is not very clear that closing a segment is an operation that is local to the segment, and not to the underlying memory source being referenced
* some extra documentation might be added to clarify that external memory sources (arrays and bytebuffers) might be aliased with multiple segments.
* some reordering in package level javadoc/MemorySegment javadoc to allow for easier concepts to introduced before more complex ones
* the javadoc for close() is not very clear that closing a segment is an operation that is local to the segment, and not to the underlying memory source being referenced
* some extra documentation might be added to clarify that external memory sources (arrays and bytebuffers) might be aliased with multiple segments.
* some reordering in package level javadoc/MemorySegment javadoc to allow for easier concepts to introduced before more complex ones
- backported by
- 
                    JDK-8248278 Improve javadoc of Foreign Memory Access API -           
- Resolved
 
-         
- 
                    JDK-8250090 Improve javadoc of Foreign Memory Access API -           
- Resolved
 
-         
- 
                    JDK-8250389 Improve javadoc of Foreign Memory Access API -           
- Resolved
 
-