Re: SRFI 207: String-notated bytevectors Daphne Preston-Kendal 18 Aug 2020 18:31 UTC

> On 18 Aug 2020, at 19:00, Marc Nieper-Wißkirchen <xxxxxx@nieper-wisskirchen.de> wrote:
>
> With your proposal, the same escape sequences mean something different in different contexts. That's worse. And it does not follow the Python model.

If I understand your objection correctly, it’s only true if you assume that regular Scheme strings are UTF-8. They’re not. It's up to an implementation to decide an internal representation, and — as in Python — semantically, they’re just bags of codepoints like #u8-vectors are bags of bytes.

\x80; in a string-notated bytevector means the byte 0x80; \x80 in a normal string means the codepoint U+0080. Those are two different things, but they can only be two different things. It's no different from the difference between  anything else in the notation: the ASCII character A in a string-notated bytevector means the byte 0x41; the ASCII character A in a string means the codepoint U+0041.

Daphne