pertsevds
When i use List.flatten() it would flatten a deep list with every nested .
iex> list = [[],["ant",["hello","hi",[[[]]]], "bat"], ["cat", "dog"]]
[[], ["ant", ["hello", "hi", [[[]]]], "bat"], ["cat", "dog"]]
iex> List.flatten(list)
["ant", "hello", "hi", "bat", "cat", "dog"]
As expected.
But when i do Stream.flat_map()
iex(6)> list = [[],["ant",["hello","hi",[[[]]]], "bat"], ["cat", "dog"]]
[[], ["ant", ["hello", "hi", [[[]]]], "bat"], ["cat", "dog"]]
iex(7)> list
[[], ["ant", ["hello", "hi", [[[]]]], "bat"], ["cat", "dog"]]
iex(8)> |> Stream.flat_map(& &1)
#Function<60.124013645/2 in Stream.transform/3>
iex(9)> |> Enum.to_list()
["ant", ["hello", "hi", [[[]]]], "bat", "cat", "dog"]
It flattens only the first level of the list. It’s a flatten() with depth == 1.
And that was not what i expected.
I needed a deep_flatten() for Stream, so i’ve made it like this:
defmodule ExTelnet.StreamDeepFlatten do
def deep_flatten(enumerables) do
deep_flat_map(enumerables, & &1)
end
def deep_flatten(first, second) do
deep_flat_map([first, second], & &1)
end
def deep_flat_map(enum, mapper) when is_function(mapper, 1) do
Stream.transform(enum, nil, fn val, nil ->
case val do
val when is_list(val) -> {deep_flat_map(val, mapper), nil}
val -> {[mapper.(val)], nil}
end
end)
end
end
Works as expected for me:
iex(2)> list = [[],["ant",["hello","hi",[[[]]]], "bat"], ["cat", "dog"]]
iex(3)> list
iex(4)> |> Stream.map(&IO.inspect(&1))
iex(5)> |> ExTelnet.StreamDeepFlatten.deep_flatten()
iex(6)> |> Stream.map(&IO.inspect(&1))
iex(7)> |> Stream.map(&("seen " <> &1))
iex(8)> |> Stream.map(&IO.inspect(&1))
iex(9)> |> Enum.to_list()
[]
["ant", ["hello", "hi", [[[]]]], "bat"]
"ant"
"seen ant"
"hello"
"seen hello"
"hi"
"seen hi"
"bat"
"seen bat"
["cat", "dog"]
"cat"
"seen cat"
"dog"
"seen dog"
["seen ant", "seen hello", "seen hi", "seen bat", "seen cat", "seen dog"]
So what i’m questioning myself now is: “Am I reinvening the wheel? Maybe there is some better simpler method and I just don’t see it?”
Trending in Discussions
The obligatory hello world thread!
Who are you and where are you from? :stuck_out_tongue:
New
Hey there,
It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
Hey folks,
I wanted to share with you a project I’ve been working on for a while: It’s an Open Source (AGPLv3) newsletter tool. Think Ma...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
In my third year of college, around 2010, I found Erlang. A few years later, I found Elixir. I liked the ideas at once: many small proces...
New
I’ve been tinkering with Lynx (by José) via hold_ledger. I used AI to write the code, a separate specification, the tests, and the Lean p...
New
Hi everyone,
I have 8 years of production experience with Erlang/OTP and I’m just starting to get to know Elixir. What would you learn f...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #elixirconf-us
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance











Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
There might be simpler way to do this, but I’m wondering what the background to this is. Can you show a practical usecase for this, where the inputs are not lists, but actual (nested) enumerables/streams?
pertsevds
Sometimes you have functions that parse some portion of text and returns . If they are included in one another we can have something like [[]] at the output.
Sebb
behaves like
Enum.flat_map/2not likeList.flatten/1pertsevds
Well, i know. But why?
lucaong
One reason:
flat_mapflattening a single level, andflattenflattening multiple levels, produces a more versatile behavior: if one needs to flatten only a single level (maybe the nested items are collections themselves and should be treated as individual items) one can useflat_map. If multiple levels should be flattened, one can callflatteninside the function called byflat_map.pertsevds
I don’t see it as that.
flattenfor lists - flattens multiple levels. So what is the word “flat” inflat_map? It’sflatten. What doesflattendo here? It’s flattening a single level. Why? It’s inconsistent withflattenfor lists.I think it should be named
concat_mapbecause of what it does. Not flattening, concatenating. And by the way, in the docs we have exactly that:Link: Enum — Elixir v1.14.2
lucaong
Another aspect is that
List.flattenis more specialized, it only flattens lists, while it leaves other collections unchanged:This makes it clear what to flatten and what not. Instead,
flat_mapflattens every enumerable:The fact that
flat_mapflattens all enumerable would make it more confusing if it were to flatten all levels: if each element is a list of maps, should the map be flattened too, or not? Flattening only one level leaves the choice to the developer.lucaong
Finally, and possibly more importantly, flattening a single level on
flat_mapis a common choice on many programming languages, making it the expected behavior for many developers.Examples are JavaScript:
Ruby:
Sebb
that’s why its called differently.
flat_mapis very handy when you map over something and you get results that you just want to omit.josevalim
Hi everyone, I believe @davaeron understands the differences between them. The question is about naming.
Correct. This is common nomenclature in all functional languages. Also add Scala and Erlang to your list.
You should read it as a “flat map operation”, i.e. as a map operation that joins its consecutive results, not as a “map plus flatten”.