From: nobu@...
Date: 2017-12-12T09:45:57+00:00
Subject: [ruby-core:84200] [Ruby trunk Feature#11256] anonymous block	forwarding

Issue #11256 has been updated by nobu (Nobuyoshi Nakada).


Just to be clear, does it require both of the definition and the use, instead of only the latter?

I mean this is allowed:

```ruby
def foo(&)
  bar(&)
end
```

but these are not:

```ruby
def foo()
  bar(&)
end

def foo(&block)
  bar(&)
end
```



----------------------------------------
Feature #11256: anonymous block forwarding
https://bugs.ruby-lang.org/issues/11256#change-68317

* Author: bughit (bug hit)
* Status: Assigned
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
* Target version: 
----------------------------------------
since capturing a block into a proc is slow: foo(&block)
and creating chains of blocks is kind of ugly and ultimately also inefficient: foo{yield}
why not allow block forwarding without capturing: foo(&) foo(1, 2, &)



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>