Le Sat, 24 Feb 2018, Drup wrote: > Shouldn't we just standardize on bunzli's libraries (including the new > https://github.com/dbuenzli/utext) instead of trying to re-write code that > usually ends up being quite subtle in each standard library ?
We could build on uutf, it's relatively small and doesn't have too many deps. However, I also don't think utf8 is that complicated that we couldn't just redo the codepoint<-> byte conversions in a simpler (and arguably lower overhead) way. In particular, `Utf8string.to_seq : t -> codepoint sequence` could be faster than calling uutf with all its poly variants. For utext, meh. It's not stable yet, and relies on a complicated non standard underlying vec structure. Ustring (or Utf8string, possibly, as it's the only reasonable string to support) should be a (possibly private) alias to string. There should be a similar Utf8buffer where you can push/pop codepoints and append other Utf8buffers. -- Simon Cruanes http://weusepgp.info/ key 49AA62B6, fingerprint 949F EB87 8F06 59C6 D7D3 7D8D 4AC0 1D08 49AA 62B6
signature.asc
Description: PGP signature
_______________________________________________ Containers-users mailing list Containers-users@lists.ocaml.org http://lists.ocaml.org/listinfo/containers-users
