The goal of the standard library is not to provide all common cases developers need, especially one that is addressed with one line of code. Instead we want you to enable you to write this code - which is possible today. This is the third proposal to the Map module this week and it is easy to see it would quickly get bloated if it was supposed to handle all of those concerns.
> * The same private function defined in many modules I personally don't see anything wrong with such a small private function defined in a handful modules. It is part of our job to break large code apart into small functions and those small functions only exist to support the current implementation. To quote Go proverbs <https://go-proverbs.github.io/>: "A little copying is better than a little dependency". > What about a pipe operator that puts the subject as the last argument? This has been proposed and rejected a couple times in this mailing list and in the forum. I would recommend you to search previous topics. :) -- 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/CAGnRm4LyAidj47FdEqpDzj8gMBS_CmAHOrU5Yu31pnmavJULyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
