Proposal: Add Enum.at!/2

[eksperimental]

Hi everyone.
I think if we have Enum.at/3 we should also have Enum.at!/2

as with Enum.at/3 there is no way to guarantee that certain index
doesn't exist, since the default value could be contained in any of the
indexes.

The only option is to use Enum.fetch!/2

what do you guys think of this?

[José Valim]

How Enum.at!/2 would be different from Enum.fetch!/2?

José Valim

www.plataformatec.com.br

Skype: jv.ptec

Founder and Director of R&D

--
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-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/20160718222830.4f1c21d4.eksperimental%40autistici.org.
For more options, visit https://groups.google.com/d/optout.

[eksperimental]

it doesn't (other than one returns a tuple and another the element
itself),
but same thing as Myron Marston mentioned,
it is useful when used in pipelines.

If we decide not to included. We should mention that in the at/3 docs.

On Mon, 18 Jul 2016 17:33:24 +0200
José Valim <jose....@plataformatec.com.br> wrote:

> How Enum.at!/2 would be different from Enum.fetch!/2?
>
>
>

> *José Valim*

[Ben Wilson]

Enum.fetch! returns simply the item itself. http://elixir-lang.org/docs/master/elixir/Enum.html#fetch!/2

fetch returns the tuples.

[eksperimental]

thank you Ben and José,
I totally missed that!

> > > > <javascript:>. To view this discussion on the web visit