From @smls

I tried to time a subroutine as follows​:

  ➜ sub a { LEAVE say now - ENTER now; sleep 1 };
  ➜ a
  ===SORRY!===
  Cannot reference undeclared local 'enter_result__1

Not sure if nesting phasers like this would be reasonable to support,
but even if not, the error message should explain what's going on in
user-friendly terms and not leak an internal variable name.

From @zoffixznet

On Mon, 03 Oct 2016 11​:59​:18 -0700, smls75@​gmail.com wrote​:

I tried to time a subroutine as follows​:

➜  sub a \{ LEAVE say now \- ENTER now;  sleep 1 \};
➜  a
===SORRY\!===
Cannot reference undeclared local 'enter\_result\_\_1

Not sure if nesting phasers like this would be reasonable to support,
but even if not, the error message should explain what's going on in
user-friendly terms and not leak an internal variable name.

Thank you for the report. This is now fixed.

Fix​: rakudo/rakudo@58de239cc90bb3a
Test​: Raku/roast@8e4f5edff7b879f9f

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

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