From: janfri26@... Date: 2019-02-08T16:35:50+00:00 Subject: [ruby-core:91497] [Ruby trunk Feature#4475] default variable name for parameter Issue #4475 has been updated by janfri (Jan Friedrich). I like the ampersand prefix of Elixir: ```elixir Enum.map [1, 2, 3], &(&1 + 2) # => [3, 4, 5] Enum.reduce [1, 2, 3], &(&1 + &2) # => 6 ``` The ampersand (&) relates more to a block in Ruby than an at-sign (@) which is associated with an instance variable context. So my preferred syntax for Ruby would be: ```ruby [1, 2, 3].map { &1 + 2 } # => [3, 4, 5] [1, 2, 3].reduce { &1 + &2 } # => 6 ``` But I'm not sure if this could be realized without syntax conflicts. ---------------------------------------- Feature #4475: default variable name for parameter https://bugs.ruby-lang.org/issues/4475#change-76757 * Author: jordi (jordi polo) * Status: Assigned * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: ---------------------------------------- =begin There is a very common pattern in Ruby: object.method do |variable_name| variable_name doing something end Many times in fact the name of the object is so self explanatory that we don't care about the name of the variable of the block. It is common to see things like : @my_sons.each { |s| s.sell_to_someone } or Account.all.each { |a| my_account << a.money } People tend to choose s or a because we have the class or the object name just there to remind you about the context. I would like to know if can be a good idea to have a default name for that parameter. I think it is Groovy that does something like: Account.all.each { my_account << it.money } Where it is automagically filled and it doesn't need to be declared. I think it is as readable or more (for newbies who don't know what is ||) and we save some typing :) =end -- https://bugs.ruby-lang.org/ Unsubscribe: