From @moritz

moritz@​hack​:~/p6/rakudo$ ./perl6-m --version
This is perl6 version 2015.07.1-717-ga6bb0ba built on MoarVM version
2015.07-108-g7e9f29e
moritz@​hack​:~/p6/rakudo$ ./perl6-m -e 'for 1, 2 { LAST say $_ }'
(Mu)
moritz@​hack​:~/p6/rakudo$ ./perl6-m -e 'for 1, 2 -> $x { LAST say $x
}'
(Mu)

I expected "2\n" as output both times.

It works when when the phaser has a separate block​:
moritz@​hack​:~/p6/rakudo$ ./perl6-m -e 'for 1, 2 -> $x { LAST { say $x } }'
2

From @usev6

Behaviour for Moar is unchanged. The code works as expected on JVM​:

$ perl6-j -e 'for 1, 2 { LAST say $_ }'
2

I added a test to S04-phasers/in-loop.t with commit Raku/roast@a1c52bacd3

BTW, this ticket looks related to the failing tests from https://rt-archive.perl.org/perl6/Ticket/Display.html?id=121722

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

From @lizmat

This test now passes, can be closed.

On 17 Jul 2016, at 21​:54, Christian Bartolomaeus via RT <perl6-bugs-followup@​perl.org> wrote​:

Behaviour for Moar is unchanged. The code works as expected on JVM​:

$ perl6-j -e 'for 1, 2 { LAST say $_ }'
2

I added a test to S04-phasers/in-loop.t with commit Raku/roast@a1c52bacd3

BTW, this ticket looks related to the failing tests from https://rt-archive.perl.org/perl6/Ticket/Display.html?id=121722

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