You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/jdk.incubator.foreign/share/classes/jdk/incubator/foreign/MemorySegment.java
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@
56
56
* A memory segment models a contiguous region of memory. A memory segment is associated with both spatial
57
57
* and temporal bounds (e.g. a {@link ResourceScope}). Spatial bounds ensure that memory access operations on a memory segment cannot affect a memory location
58
58
* which falls <em>outside</em> the boundaries of the memory segment being accessed. Temporal bounds ensure that memory access
59
-
* operations on a segment cannot occur after the resource scope associated with a memory segment has been closed (see {@link ResourceScope#close()}).
59
+
* operations on a segment cannot occur <em>after</em> the resource scope associated with a memory segment has been closed (see {@link ResourceScope#close()}).
60
60
* <p>
61
61
* All implementations of this interface must be <a href="{@docRoot}/java.base/java/lang/doc-files/ValueBased.html">value-based</a>;
62
62
* programmers should treat instances that are {@linkplain Object#equals(Object) equal} as interchangeable and should not
@@ -157,7 +157,7 @@
157
157
* scope, it can only be accessed by the thread which owns the scope.
158
158
* <p>
159
159
* Heap and buffer segments are always associated with a <em>global</em>, shared scope. This scope cannot be closed,
160
-
* and can be considered as <em>always alive</em>.
160
+
* and segments associated with it can be considered as <em>always alive</em>.
0 commit comments