From @masak

<masak> rakudo​: my %info = x => 1, y => 2; my ($x, $y) := %info; say
($x, $y).perl
<p6eval> rakudo 684fdf​: OUTPUT«Not enough positional parameters
passed; got 1 but expected 2␤ in 'infix​:<​:=>' at line 1␤ in main
program body at line 22​:/tmp/kudgcUuXVo␤»
<masak> jnthn​: should something like that work?
<jnthn> masak​: Can't remember if you need to explicitly capture-ize the RHS
<jnthn> rakudo​: my %info = x => 1, y => 2; my ($x, $y) := \%info; say $x, $y;
<p6eval> rakudo 684fdf​: OUTPUT«Not enough positional parameters
passed; got 1 but expected 2␤ in 'infix​:<​:=>' at line 1␤ in main
program body at line 22​:/tmp/LsMKGXbXkQ␤»
<jnthn> er, wtf
<jnthn> I'm sure that _did_ work...
<masak> yeah
<jnthn> oh, wait
<jnthn> rakudo​: my %info = x => 1, y => 2; my (($x, $y)) := %info; say $x, $y;
<p6eval> rakudo 684fdf​: OUTPUT«12␤»
<jnthn> ah.
<jnthn> That's telling.
<masak> jnthn​: can I submit as a rakudobug that it doesn't work
without the double parens?
<jnthn> masak​: Check if the spec says it should first.
<masak> oki.
<masak> jnthn​: hm.
<masak> (​:@​even, :@​odd) := |classify { $_ % 2 ?? 'odd' !! 'even' }, @​list;
<masak> seems the | is needed, too.
<masak> rakudo​: my %info = x => 1, y => 2; my ($x, $y) := |%info; say
($x, $y).perl
<p6eval> rakudo 684fdf​: OUTPUT«Not enough positional parameters
passed; got 1 but expected 2␤ in 'infix​:<​:=>' at line 1␤ in main
program body at line 22​:/tmp/1QbM2ij3UZ␤»
<masak> but that doesn't work either, so... :)
* masak submits rakudobug
<jnthn> I'm not sure | knows what to do there
<jnthn> oh, or maybe it does...but does something wrong, hmm
<jnthn> I bet there's some screw-up somehwere in coercion to capture.

From @timo

< benabik> r​: my @​list = 1..4; my (@​even, @​odd); :(​:@​even, :@​odd) :=
classify { $_ % 2 ?? 'odd' !! 'even' }, @​list; say @​even, @​odd
<+p6eval> rakudo 7794ed​: OUTPUT«2 41 3␤»
< timotimo> r​: my @​list = 1..4; my (​:@​even, :@​odd) := classify { $_ % 2
?? 'odd' !! 'even' }, @​list; say @​even, @​odd
<+p6eval> rakudo 7794ed​: OUTPUT«2 41 3␤»

Although the exact way to do this has changed since this ticket was
created, it's implemented and apparently working as intended now.

Added a test to roast in 817476a. (t/spec/S02-names-vars/signature.t)

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

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