Re: RFR: 8391678: Correct encoding wording and destination bound in MemorySegment.copy(String, Charset, int, MemorySegment, long, int)

[Per Minborg]

On Wed, 2 Sep 2026 20:40:03 GMT, Liam Miller-Cushon <cus...@openjdk.org> wrote:

> This change fixes some inaccuracies in the javadoc for methods introduced in 
> [JDK-8369564](https://bugs.openjdk.org/browse/JDK-8369564).
> 
> In addition to the issues reported in 
> [JDK-8391678](https://bugs.openjdk.org/browse/JDK-8391678) I took a pass over 
> the rest of the javadoc introduced in 
> [JDK-8369564](https://bugs.openjdk.org/browse/JDK-8369564) and fixed a 
> related issue in `SegmentAllocator.allocateFrom`.
> 
> 
> ---------
> - [x] I confirm that I make this contribution in accordance with the [OpenJDK 
> Interim AI Policy](https://openjdk.org/legal/ai).

Does the changed wording in the `SegmentAllocator`'s return clause require a 
CSR?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/32663#issuecomment-5521886193