Ha Ha, now Scyer Prolog wants also
byte friendly compact strings:

2. introduce a compact internal representation for lists of bytes,
which appear to Prolog programs as lists of characters.
https://github.com/mthom/scryer-prolog/blob/master/src/lib/crypto.pl#L867C2-L868C63

But they motivated it by security concerns,
whereas my concern was to get rid of ISO-ism
making a distinction between text and byte streams,

on the Prolog API levels. It would be all codes.

Mostowski Collapse schrieb:
> - UTF-16 native strings: Does work well with the envisioned
> "latin1" payload, the range 0..255 is encoded in one 16-bit word,
> which is two bytes, but most programming language already
> implement clever strings:
>
> JEP 254: Compact Strings
> We propose to change the internal representation of the String class
> from a UTF-16 char array to a byte array plus an encoding-flag field.
> The new String class will store characters encoded either as ISO-8859-1/
> Latin-1 (one byte per character), or as UTF-16 (two bytes per character),
> based upon the contents of the string. The encoding flag will indicate
> which encoding is used.
> https://openjdk.org/jeps/254