Hello beloved core team, TLDR; Should we have Access.get_lazy/3 ?
As usual I'm sure there is some reason why this doesn't exist yet but I don't know so here is the question/proposal: We have Map.get_lazy/3 and Keyword.get_lazy/3 - they're amazing and helpful. Access basically encapsulates the 2 and I generally use it where I can to allow both Keywords and Maps - most commonly when I deal with options. It doesn't have get_lazy/3 though, which sometimes makes me fall back to either Map or Keyword (or wrap it myself). Using Access.fetch/2 it should also be easy to implement. So, would a PR implementing Access.get_lazy/3 be considered? Thanks! Tobi -- 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 elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAG3Z5YQYuv8SF81vs8UNhtpGN3wA0NHgH1yFhixuwoQmV2S8eQ%40mail.gmail.com.
