Catherine
Catherine
Or maybe `Uchar.of_char '%c'` for printable and `Uchar.of_int 0x%04X` for non-printable...
You can conservatively stick to ASCII. 0x20..0x7E?
> > > > Sorry, can you expand on that? I mean, convert it to `int` and check that it's between `0x20` and `0x7E`. That should cover all printable ASCII...
You need to skip `0x00` to `0x1F` inclusive, too.
Oh sorry, I missed `Char.escaped`. You are right.
Yes, I believe that is the right place to implement support for `Uchar.t`.
Why not both? The stdlib/compiler changes will likely take a lot of time.
@pmetzger I like the syntax.
I think `[@@warning "-32"]` and `[@deriving pp]` both seem like good options; we can simply do both of them.
@NathanReb As mentioned above in https://github.com/ocaml-ppx/ppx_deriving/issues/171#issuecomment-400598844, I think both `[@@warning "-32"]` and `[@deriving pp]` ought to be implemented. If you can do one of them, great!