You can just switch-match on trusted types, then it even looks modern. :)
Gruß,
Bernd
--
https://bernd.eckenfels.net
Von: core-libs-dev <core-libs-dev-r...@openjdk.org> im Auftrag von Chen Liang <li...@openjdk.org>
Gesendet: Montag, März 17, 2025 3:25 AM
An: core-libs-dev@openjdk.org <core-libs-dev@openjdk.org>; nio-...@openjdk.org <nio-...@openjdk.org>
Betreff: Re: RFR: 8343110: Add getChars(int, int, char[], int) to CharSequence and CharBuffer
On Sat, 15 Mar 2025 23:30:21 GMT, Markus KARG <d...@openjdk.org> wrote:
Gesendet: Montag, März 17, 2025 3:25 AM
An: core-libs-dev@openjdk.org <core-libs-dev@openjdk.org>; nio-...@openjdk.org <nio-...@openjdk.org>
Betreff: Re: RFR: 8343110: Add getChars(int, int, char[], int) to CharSequence and CharBuffer
> Some good reason to *not* adopt my proposal?
I am still afraid of such a pattern in the future like:
CharSequence cs = ...
if (cs.getClass().getModule() == Object.class.getModule()) {
// or cs.getClass().getClassLoader() == null
cs.getChars(...);
} else {
// damn, can't trust an arbitrary char sequence!
char[] intermediate = ...
cs.getChars(...);
// copy from intermediate etc.
}
-------------
PR Comment: https://git.openjdk.org/jdk/pull/21730#issuecomment-2727862188