Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8235836

Cleanup memory access API javadoc

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: repo-panama
    • Fix Version/s: repo-panama
    • Component/s: core-libs
    • Labels:
      None

      Description

      The CSR review outline the following issues in the memory access API javadoc:

      * Typo in MemoryLayout "for a finite sequence layout S whose element layout is E and size is L" "L" is not italicized.

      * typo in MemoryAddress.equals Returns true if and only if the specified object is also a address, and it is equal to this address.

      * If MemoryAddress are equal if their offsets and segments are equal, that should be stated explicitly.

      * Is it the case that there is a memory leak one of the threads that has acquired a memory segment dies without freeing it? Better document this condition in MemorySegment::acquire

      * MemoryLayout.byteAlignment() should have an @implSpec tag describing its default implementation.

      * For MemoryLayout.equals, what aspects are compared? In particular, would a GroupLayout with and without a name be considered equal?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mcimadamore Maurizio Cimadamore
              Reporter:
              mcimadamore Maurizio Cimadamore
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: