No, what I mean is that, when you're writing a generic parser, you read #u8, and then you can do...
  (case (peek-char port)
     ((#\")  (read-textual-bytestring port))  ;; read #u8"..."
     ((#\()  (list->bytevector (read port)))   ;; read #u8(...)
     (else (error ...)))


On Wed, Oct 14, 2020 at 10:51 AM Wolfgang Corcoran-Mathe <xxxxxx@sigwinch.xyz> wrote:
On 2020-10-14 09:19 -1000, Shiro Kawai wrote:
> Yeah including the leading double-quote may be good.  From parser's
> perspective, after reading #u8 it can peek at the next char to dispatch.

So is the idea to accept both '#u8foo"' and '#u8"foo"'?  Maybe I've
misunderstood.  I'd like the leading #\" to either be part of the
prefix or part of the content, but not optional.

--
Wolfgang Corcoran-Mathe  <xxxxxx@sigwinch.xyz>

"The composer makes plans, music laughs." --Morton Feldman