Unfortunately I think this patch causes the following to fail: sub foo($a) { 1.say for $a }
foo((1,2,3)); The problem is that simply looking at (misnamed) Perl6Scalar and deciding what to do is a little coarse-grained. The real problem is in the argument binding to a scalar versus array variable. We'll probably revisit this as part of updating parameter passing semantics. In the meantime, reopening the ticket until the above case is resolved also. Pm