From: sawadatsuyoshi@... Date: 2014-10-18T05:30:17+00:00 Subject: [ruby-core:65778] [ruby-trunk - Feature #10394] An instance method on Enumerator that evaluates the block under with self being the block variable. Issue #10394 has been updated by Tsuyoshi Sawada. If one wants to go with a non-letter method name, `|` may be a candidate: ~~~ruby ["foo", "bar"].map.|{upcase} ["foo", "bar"].map.|{concat("ber")} [" foo ", "\tbar\n"].map.|{strip.upcase} ~~~ The `|` character here is reminiscent of the unix pipe, which may be interpreted here as pass the values to the block, and it also resembles the `||` notation in the block. But I don't know if people might think that ugly. A word-like name may also be good. If the name is less than five characters, then it would need less typing than the original form, (i.e., five-letter name `.xxxxx{foo}` would require as much typing as `{|x| x.foo}`. ---------------------------------------- Feature #10394: An instance method on Enumerator that evaluates the block under with self being the block variable. https://bugs.ruby-lang.org/issues/10394#change-49514 * Author: Tsuyoshi Sawada * Status: Feedback * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- **Background** There has been desire to omit the `| |` and the explicit receiver in a block used with an enumerator or an enumerable. Currently, when the content of the block is a single method that takes no argument, symbol-to-proc is used with the `&` syntax so that: ~~~ruby ["foo", "bar"].map{|s| s.upcase} ~~~ can be written as: ~~~ruby ["foo", "bar"].map(&:upcase) ~~~ There has repeated been proposals (#8987, #9076, #10318) that express this desire to do this even when the block involves a method chain or a method with arguments like the following: ~~~ruby ["foo", "bar"].map{|s| s.concat("ber")} [" foo ", "\tbar\n"].map{|s| s.strip.upcase} ~~~ Focus has been on modifying how a block is passed to the enumerable/enumerator, and there has not been consensus on how the syntax should be. **Proposal** Unlike the earlier proposals, I suggest that there should be an instance method on `Enumerator`, let's say `Enumerator#as_self`, that evaluates the block each time with `self` being the block variable that would be passed otherwise. With such method, the cases above would be written like this: ~~~ruby ["foo", "bar"].map.as_self{concat("ber")} [" foo ", "\tbar\n"].map.as_self{strip.upcase} ~~~ This adds no modification to the syntax, it just requires a new method `Enumerator#as_self` to be implemented. I consider this method being along the lines of `Enumerator#with_index`, `Enumerator#with_object`; it intervenes between an enumerator (related to a block-taking method) and a block, and let the block-taking method work in a modified way. It resembles `instance_eval`, but is different in that it assigns to `self` what would be a block variable (which changes for each iteration), instead of assigning the receiver. -- https://bugs.ruby-lang.org/