From @masak

<lizmat> m​: sub a ($a,$b) { say $a; say $b }; my $c = \(42, b=> 1);
a(|$c) # this should never work, right? (receiving a pair in $b)
<camelia> rakudo-moar ddfb57​: OUTPUT«Not enough positional parameters
passed; got 1 but expected 2 [...]
* lizmat is looking at a possible bogus test in "t/spec/S02-types/capture.t
<TimToady> yes, incorrect
<lizmat> => is a Pair creator, not? regardless of quoting or nor ?
<TimToady> but quotes or parens should suppress named arg interpretation
<lizmat> so that would indicate a problem in the capture creation
<TimToady> m​: my $c = \(42, "b" => 1); say $c.elems
<camelia> rakudo-moar ddfb57​: OUTPUT«1␤»
<TimToady> m​: my $c = \(42, "b" => 1); say $c.keys
<camelia> rakudo-moar ddfb57​: OUTPUT«0 b␤»
<TimToady> that's wrong
<TimToady> should have 2 elems, and the 2nd should just be a pair
* masak submits rakudobug
* TimToady is kinda surprised it's working in Real Life when it's not
working there
<TimToady> implies there are two code paths where there probably oughta be one

From @jnthn

On Mon Aug 18 10​:09​:12 2014, masak wrote​:

<lizmat> m​: sub a ($a,$b) { say $a; say $b }; my $c = \(42, b=> 1);
a(|$c) # this should never work, right? (receiving a pair in $b)
<camelia> rakudo-moar ddfb57​: OUTPUT«Not enough positional parameters
passed; got 1 but expected 2 [...]
* lizmat is looking at a possible bogus test in "t/spec/S02-
types/capture.t
<TimToady> yes, incorrect
<lizmat> => is a Pair creator, not? regardless of quoting or nor ?
<TimToady> but quotes or parens should suppress named arg
interpretation
<lizmat> so that would indicate a problem in the capture creation
<TimToady> m​: my $c = \(42, "b" => 1); say $c.elems
<camelia> rakudo-moar ddfb57​: OUTPUT«1␤»
<TimToady> m​: my $c = \(42, "b" => 1); say $c.keys
<camelia> rakudo-moar ddfb57​: OUTPUT«0 b␤»
<TimToady> that's wrong
<TimToady> should have 2 elems, and the 2nd should just be a pair
* masak submits rakudobug

The test is now passing and unfudged.

* TimToady is kinda surprised it's working in Real Life when it's not
working there
<TimToady> implies there are two code paths where there probably
oughta be one

Indeed, and now there is one code-path as of Rakudo commit 253bb58.

Resolvin'

The RT System itself - Status changed from 'new' to 'open'

@jnthn - Status changed from 'open' to 'resolved'