My 2 cents: when faced with this in the past I've leaned on the syntax
employed in multi-module aliasing, ie
Foo.bar/{1, 2}
I like the consistency. It just occurred to me that the parenthetical
approach of this could be conducive to supporting ranges as well, such as
Foo.bar/{1..3}
--
You re
Small nit:
Currently Elixir pushes users to call Erlang when working with crypto. This
> doesn't align with Elixirs goal of developer productivity.
I've always found the ability to dip into erlang a major factor of Elixir's
promise of developer productivity. :D
I agree with the sentiment that
I agree with a separate org. I picked here to start simply because most of
the code out there that has relevant pieces probably belongs to someone on
this mailing list. I think that once it is stable it may be a candidate for
inclusion. But until it is stable I wouldn't consider it.
I also agr
On Thu, Oct 4, 2018 at 1:04 PM Fernando Tapia Rico
wrote:
> Would we use this for functions with default arguments too or only for
>> custom multiple-arity functions which relate to each other?
>>
>
> Just for the latter, but good catch!
>
> To give more examples, I wouldn't use the new syntax wi
>
> Would we use this for functions with default arguments too or only for
> custom multiple-arity functions which relate to each other?
>
Just for the latter, but good catch!
To give more examples, I wouldn't use the new syntax with `Map.get/3`, but
I'll definitely use it for `Task.async/1,3`
>
> Regarding ExDoc, I would use the first arity to create the link (Erlang
> documentation seems to do the same). For example `Module.fun/1,2` would
> link to `Module.html#fun/1`; and `Module.fun/4,3` to `Module.html#fun/4`. I
> like this option because it allows developers to control were the lin
