On Mon, 26 Jun 2023 16:02:57 GMT, Chen Liang wrote:
> This is just a copycat of the original newStringNoRepl, which should be
> fixed; newStringUTF8NoRepl has no such issue.
Unfortunately, the behavior of `newStringUTF8NoRepl` is not the same as that of
`newStringNoRepl`, as it actually always
> Added a new method `newStringLatin1NoRepl` to the `JavaLangAccess`.
>
> Reasons:
>
> * Most use cases of `newStringNoRepl` use `ISO_8859_1` as the charset,
> creating a new shortcut can make writing shorter;
> * Since all possible values of `byte` are legal Latin-1 characters,
> `newStringLat
