I’m implementing a custom log formatter and I wanted to parse the lists returned by SASL except they seem to be weird: iex(1)> msg = ["Application ", "logger", " started at " | ":nonode@nohost"] ["Application ", "logger", " started at " | ":nonode@nohost"] iex(2)> is_list msg true iex(3)> is_binary…

[image] NobbZ: This is like this due to performace reasons and relying on the assumption, that one does not produce improper lists, since there is simply no reason to do so… There are reasons to use improper lists. The most common example, in Erlang/Elixir is iolists . These are desirable fo…

Weird SASL lists and can I rely on Kernel.is_list?

Questions / Help

JEG2 May 1, 2016, 3:09pm 12

Yeah, you would need to walk it checking for an improper tail at each step.

2 Likes

What can you do with improper lists?