[ruby-core:92096] Re: [Ruby trunk Misc#15723] Reconsider numbered parameters

["Martin J. Dürst" <duerst@it.aoyama.ac.jp>]

On 2019/04/02 01:07, Austin Ziegler wrote:
> In general, I’m OK with this change, but I think that there’s a possible
> scoping issue with these automatic variables that I’m not sure that has
> been considered:
> 
> outer.each {
>    puts @1
>    @1.each {
>      puts @1
>    }
> }
> 
> Elixir doesn’t have this issue because you *can’t* declare nested
> declarations this way. But in Ruby, you would no longer have access to the
> outer `@1`.

Maybe that's a feature. Ideally, @1,... are only used for very simple 
cases, and nesting isn't really that simple.

Regards,   Martin.

> I’m not sure what other languages similar to Ruby do.



>> ----------------------------------------
>> Misc #15723: Reconsider numbered parameters
>> https://bugs.ruby-lang.org/issues/15723#change-77387
>>
>> * Author: sos4nt (Stefan Schüßler)
>> * Status: Feedback
>> * Priority: Normal
>> * Assignee:
>> ----------------------------------------
>> I just learned that *numbered parameters* have been merged into Ruby
>> 2.7.0dev.
>>
>> For readers not familiar with this feature: it allows you to reference
>> block arguments solely by their *index*, e.g.
>>
>> ```ruby
>> [1, 2, 3].each { |i| puts i }
>>
>> # can become
>>
>> [1, 2, 3].each { puts @1 }
>> ```
>>
>> I have an issue with this new feature: I think **it encourages sloppy
>> programming** and results in **hard to read code**.
>>
>> ---