From: "jeremyevans0 (Jeremy Evans)" Date: 2021-11-18T20:55:47+00:00 Subject: [ruby-core:106158] [Ruby master Feature#11256] anonymous block forwarding Issue #11256 has been updated by jeremyevans0 (Jeremy Evans). mame (Yusuke Endoh) wrote in #note-16: > @matz accepted this, but said that the formal argument must explicitly receive a anonymous block parameter, i.e. > > ``` > def foo(&) = bar(&) # OK > def foo = bar(&) # NG > ``` > > In the future, matz wants to make it more explicit whether a method accepts a block or not. > > @jeremyevans0 Could you remove my diff from your PR? Sure, I updated the pull request. This made the pull request much simpler: https://github.com/ruby/ruby/pull/5051 ---------------------------------------- Feature #11256: anonymous block forwarding https://bugs.ruby-lang.org/issues/11256#change-94760 * Author: bughit (bug hit) * Status: Assigned * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- 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: