Lists of integers are charlists, which is the default string type for erlang. For a decoding library there’s no way to know if your intend was to transfer a string encoded as a charlist or an actual list of integers.
LostKobrakai
KalleJoP
Okay, I understand.
In my use case, there is no need to decode charlists, so I may be able to fix the decoding “issue”.
Another idea I have is to add an empty string or something similar as the first item in the list to prevent it from containing only integers.
What would be the best approach to work around this behavior?
0
Nicd
Not sure what you mean by this, as even the link you gave points out:
A Unicode string in Erlang is a list containing integers, where each integer is a valid Unicode code point and represents one character in the Unicode character set.
That’s what charlists are. You need to use the unicode module to convert to binary as you must choose which binary encoding to use (typically you want UTF-8).
0
paulanthonywilson
Well
iex(1)> :unicode.characters_to_binary(['hello matey ', [129335, 8205, 9792, 65039]])
"hello matey 🤷♀️"
2
Nicd
rvirding
Creator of Erlang
The 107 in the binary indicates that it is STRING_EXT, a string, which is lan optimisation for a list of bytes, while 108 indicates a LIST_EXT which is for a list where you specify each element and a tail.
6