From: "Matthias Wächter" <matthias@...>
Date: 2011-12-09T17:56:24+09:00
Subject: [ruby-core:41567] Re: [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong

Matz,

On 09.12.2011 09:44, Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: [ruby-core:41561] Re: [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong"
>      on Fri, 9 Dec 2011 17:31:31 +0900, Matthias W��chter<matthias@waechter.wiz.at>  writes:
> |
> |Hi Matz,
> |
> |Please excuse my ignorance, but why do we want this auto-splat behavior
> |in Ruby at all? For me this goes very much against the POLS. Has this
> |been discussed or documented somewhere for reference?
>
> Yes, we have been discussed very deeply in the past, mostly in
> ruby-dev (Japanese developers list).  In tha past history of Ruby,
> assignment to block parameters had behaved more like multiple
> assignment.  But we have gradually moved toward method argument
> passing behavior.  So if I were about to start new language, I
> wouldn't add this auto-splat at all, but since we have history, the
> community and the code base, I couldn't fix this corner-case.

Thanks for your explanation. So I���m not the only one wondering ���

> Maybe we can remove this in Ruby 3.0.

+1

> 							matz.

��� Matthias