If we're considering composability, this is a bad idea, yes. Adding it (and
the likes) to Map would encourage people to use those for maps instead of
Enum, which would be a noticable performance impact (a factor log n
slower).
I'd vote for not including this feature, because of the damage it might do
by leading people away from Enum.
On Saturday, June 18, 2016 at 6:27:07 PM UTC+2, Filip Haglund wrote:
>
> I wish there was a Map.filter_values function that would filter on keys or
> values, but leave the other one intact. This seems like something that
> should be in the standard library.
>
> Example implementation of a Map.filter_values that would filter a map
> based on its values, leaving the keys intact:
>
> @doc """
> Filter map based on its values, leaving the corresponding keys intact.
> """
> @spec map_filter_values(Map.t, (any -> boolean)) :: Map.t
> def map_filter_values(map, func) do
> map |> Enum.filter(fn {_, val} -> func.(val) end) |> Map.new
> end
>
>
>
> A corresponding Map.filter_keys would also be nice.
>
--
You received this message because you are subscribed to the Google Groups
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elixir-lang-core/16d8f065-9fd8-44b6-b9ea-69025699fb3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
