I’m not involved in the decision except as discussing it as a possibly interested user.
My concern is that `operation_by` hides a potentially useless `Enum.filter/2`, resulting in 2n loops over the enumerable list. `for` comprehensions and `Enum.reduce/2,3` make the filtering part of the list, and the use of Stream operations does something _similar_ while leaving the expressiveness that `operation_by` may hide. If we could figure out a way to implement something like `operation_by` without the filter pass so that it operates more efficiently than `list |> Enum.filter(filter) |> <enum-operation>(operation_fn)`, I think that it becomes much easier to argue. -- 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/CAJ4ekQt8%3D0nyT6zy5jZEu4_o8u7PZ%2BUd0Ygp0ne5ffwDyvUeHQ%40mail.gmail.com.
