idi527
Is there a way to compare iolists for equality without converting them to binary?
Or is a custom function needed?
Something like (currently incorrect, doesn’t account for nested lists):
defmodule Comparer do
@moduledoc """
Equality comparison for iolists consisting of binaries.
"""
@spec equal?(iolist, iolist) :: boolean
def equal?(iolist1, iolist2)
def equal?(iolist1, iolist2) do
equal?(iolist1, iolist2, [])
end
defp equal?(
[<<char, rest_bin1::bytes>> | rest_iolist1],
[<<char, rest_bin2::bytes>> | rest_iolist2],
[]
) do
equal?([<<rest_bin1::bytes>> | rest_iolist1], [<<rest_bin2::bytes>> | rest_iolist2], [])
end
defp equal?(
[<<>> | rest_iolist1],
[<<>> | rest_iolist2],
[]
) do
equal?(rest_iolist1, rest_iolist2, [])
end
defp equal?(
[<<>> | rest_iolist1],
iolist2,
[]
) do
equal?(rest_iolist1, iolist2, [])
end
defp equal?(
iolist1,
[<<>> | rest_iolist2],
[]
) do
equal?(iolist1, rest_iolist2, [])
end
defp equal?(
[<<char, rest_bin1::bytes>> | rest_iolist1],
rest2,
[<<char, rest_bin3::bytes>> | rest_buffer2]
) do
equal?([<<rest_bin1::bytes>> | rest_iolist1], rest2, [<<rest_bin3::bytes>> | rest_buffer2])
end
defp equal?(
[<<>> | rest_iolist1],
rest2,
[<<>> | rest_buffer2]
) do
equal?(rest_iolist1, rest2, rest_buffer2)
end
defp equal?(
[<<>> | rest_iolist1],
rest2,
buffer2
) do
equal?(rest_iolist1, rest2, buffer2)
end
defp equal?([], [], []) do
true
end
defp equal?(_, _, _) do
false
end
end
Marked As Solved
NobbZ
Equality is easy, just use ==/2. But I fear it’s equivalency you want to check. And to be honest, I think flushing them into binary and compare equality on those should be the easiest thing.
Also Liked
hauleth
@NobbZ already told you that equality != equivalence, but let see why you cannot compare iolists and why your comparator is terribly wrong.
See what Typespecs say about iolist type:
iolist()maybe_improper_list(byte() | binary() | iolist(), binary() | [])
But what is improper list?
So all of us get used to it that list in Erlang is head and tail or an empty list (yes empty list is special case of list). So when we do [a | b] = list then is_list(b) == true. Simple. But what when it isn’t? Nothing in Erlang prevents you from doing [1 | 2]. Yes this is proper syntax, yes it will compile, yes it is used. This is called improper list and your Comparer will fail on that.
Second thing is that iolist can be:
- infinitely nested, so
[[[[[["a"]]]]]]is also properiolistthat is equivalent to["a"] - can contain raw bytes, so
["a", 97]is equivalent to["aa"] - can contain Erlang strings, which are lists
['a'] == [[97]] == [[?a]]which is equivalent to["a"]
So some hard examples for you to compare:
["foo", 'bar' | ?z]vs[["foo" | "bar"], "z"]['a' | "ą"]vs["aą"]["aa", ?a, 'aa']vs["a", ?a, 'aa' | "a"]
rvirding
None that I know of. The thing to be aware of is that there is no real iolist data type, it is just a nested recursive structure which happens to be interpreted in a special way in some cases. The main one being that on output the BEAM will automagically flatten it and output the bytes. This means that in many case you don’t have to pay the price of flattening it.
That should be all now. 
rvirding
The reason converting the iolists to binaries and then doing and equals test is that these are both implemented in the VM in C while your code is in Elixir. No, will not go faster if you were to write it in Erlang. [*]
You can probably make your code more efficient when comparing binaries by directly comparing the longest leading chunk in one go instead of doing it byte by byte. And it is fun code to write as well. Another fun function is one that takes an iolist and returns the Nth byte.
[*] Of course the Erlang would be more beautiful. 
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Real-time error tracking, performance insights, and observability for devs.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Real-time error tracking, performance insights, and observability for devs.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"