On Tue, Jun 6, 2023 at 10:39 AM wrote:
Basically, it just means to allow strings and character literals as
> elements of byte vectors written as "#u8(...)".
>
Any strings and characters, or just ASCII ones?
\This is incompatible to SRFI-4 but similar to SRFI-207.
>
Any particular reason not
Hi!
Kristian Lein-Mathisen suggested an extension to the bytevector syntax
for SRFI-4 and R7RS bytevectors (which becomes more relevant in the
forthcoming UTF-aware CHICKEN) which seems quite practical. I'd be
eager to know how useful other users consider this feature before I
submit a patch.