From @lizmat

<lizmat> m​: class A { method sink() { print "sunk " } }; my @​a = A.new xx 10 # looks like assigning it is sinking?
<camelia> rakudo-moar 915f45​: OUTPUT«sunk sunk sunk sunk sunk sunk sunk sunk sunk sunk »
<lizmat> this shouldn't happen, now should it ?
<jnthn> lizmat​: That sinking looks wrong, yeah. I mean, sinking implies "this value is being thrown away", and storing it in a variable is certainly not throwing it away :)
<lizmat> jnthn​: ok, looking into it
<lizmat> actually, looks like xx is sinking it

From @zoffixznet

Looks like this was fixed​:

<Zoffix> m​: class A { method sink() { print "sunk " } }; my @​a = A.new xx 10
<camelia> rakudo-moar ac0dcd​: ( no output )

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

From @lizmat

On 15 Jun 2016, at 05​:33, Zoffix Znet via RT <perl6-bugs-followup@​perl.org> wrote​:

Looks like this was fixed​:

<Zoffix> m​: class A { method sink() { print "sunk " } }; my @​a = A.new xx 10
<camelia> rakudo-moar ac0dcd​: ( no output )

Indeed, fixed with 0ef135a52207d376df3

Liz

From @zoffixznet

Tests added​: Raku/roast@6fd8bbb9c8

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