From damian@conway.org

The following test program demonstrates that, under Rakudo perl6 version
2014.04 built on MoarVM version 2014.04, a FIRST block is only called if
a loop block is actually executed, but a LAST block is called even the
block is skipped. This seems inconsistent and certainly makes FIRST/LAST
less useful. The behaviour of FIRST seems correct; the behaviour of LAST
seems wrong.

Specifically, I expected to get​:

  {1, 2, 3, }

but I got​:

  {1, 2, 3, }
  }

which seems to suggest LAST isn't quite right yet.

Damian

-----cut----------cut----------cut----------cut----------cut----------cut----------cut-----

use v6;

my @​list;

@​list = 1..3;
for (@​list) -> $n {
  FIRST { print '{' }
  print "$n, ";
  LAST { say '}' }
}

@​list = ();
for (@​list) -> $n {
  FIRST { print '{' }
  print "$n, ";
  LAST { say '}' }
}

-----end----------end----------end----------end----------end----------end----------end-----

From @masak

Commit 1bb76a6 in roast adds a test (in S04-phasers/in-loop.t) for the expectation expressed in this ticket​: that LAST not fire if the loop doesn't have iterations.

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

From @jnthn

On Mon Jun 02 14​:06​:49 2014, masak wrote​:

Commit 1bb76a6 in roast adds a test (in S04-phasers/in-loop.t) for the
expectation expressed in this ticket​: that LAST not fire if the loop
doesn't have iterations.

Fixed in bec414d in Rakudo; resolving.

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