I can’t think of cases where I wouldn’t want `@doc delegate_to` generated for 
me or where I would use it explicitly.


> On 22 Nov 2019, at 20:11, Rich Morin <[email protected]> wrote:
> 
>> On Nov 22, 2019, at 10:58, Wojtek Mach <[email protected]> wrote:
>> 
>>   ~/src/elixir[master]% rg delegate_to
>>   lib/elixir/lib/kernel.ex
>>   4909:        @doc delegate_to: {target, as, :erlang.length(as_args)}
> 
> Amazing how much one line of code can do, when it's the right line in the
> right place.  Anyway, I gather that the upcoming release of Elixir will
> generate "@doc delegate_to" lines automagically and I will be able to
> remove the ones I've added.  Nice.
> 
> FWIW, I had suggested a :doc flag in case there were cases where folks
> wouldn't want the "@doc delegate_to" to be generated.  I take it that this
> isn't a concern?  Also, now that this feature is being added, is there a
> separate use case for adding an explicit "@doc delegate_to" line?
> 
> -r
> 
> 
> 
> -- 
> 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/BA448C06-C519-4CFE-93EF-8DBED5AE94ED%40gmail.com.

-- 
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/5FC76DAC-9842-469F-81B4-141DF3C1B4D9%40wojtekmach.pl.

Reply via email to