<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<br>
<div>
<blockquote type="cite">
<div>On Jul 2, 2025, at 11:19 AM, Alan Bateman <alan.bateman@oracle.com> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>On 02/07/2025 16:58, Brett Okken wrote:<br>
<blockquote type="cite" cite="mid:CANBJVOGVYfJwUxFfqx_-UrvhDCpLenD=Wi_rRMXBHpZ7F=jTTQ@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">:
This makes it very difficult to pass a CharBuffer (where the position
is not 0) to an api taking a CharSequence - because if that api makes
a switch to start using getChars (rather than charAt), it will break.
</pre>
</blockquote>
Thanks for bringing this up. It does need attention. I just chatted with Brian Burkhalter so he's going to look through the spec + implementation changes to address this. If there is any risk or uncertainty then it mean pulling this out.<br>
</div>
</div>
</blockquote>
<br>
</div>
<div>It looks like only CharBuffer.getChars is broken so the rest of the change can stay. I filed this issue to track it:</div>
<div><br>
</div>
<div><a href="https://bugs.openjdk.org/browse/JDK-8361299">https://bugs.openjdk.org/browse/JDK-8361299</a></div>
<div><br>
</div>
<div>The fix is straightforward but will break a test and require a CSR.</div>
<div><br>
</div>
<div>Brian</div>
</body>
</html>