Sun Oct 24 10:35:08 CEST 2021
I was wondering if there was interest in modifying the io interpretation
of "~ts" to allow an integer between the t and s for forcing a
particular unicode interpretation. That would allow a list of bytes to
be interpreted as UTF8, to provide the same output as a binary:
I was also wondering if bytestring types would be added to Erlang/OTP, like:
-type nonempty_bytestring() :: nonempty_list(byte()).
-type bytestring() :: list(byte()).
They are useful in iolists to ensure only bytes (not other integers) are
in nested lists.
More information about the erlang-questions