From @masak

< masak> r​: sub { sub foo($x = return) { $x }; say foo }(); say "alive"
<camelia> rakudo-jvm bbdcfd​: OUTPUT«alive␤»
<camelia> ..rakudo-moar bbdcfd​: OUTPUT«Attempt to return outside of
any Routine [...]
<camelia> ..rakudo-parrot bbdcfd​: OUTPUT«alive␤Nominal type check
failed for parameter '$x'; expected Any but got Mu instead␤»
<masak> hey, but that's a moarbug right there...
* masak submits moarbug

rakudo-jvm has this one right. rakudo-parrot fails because of another
known effect, reported in RT #​122325. rakudo-moar seems to be under
the impression that the parameter list isn't part of the routine. But
it is; at the point the parameters bind, we're already "running" the
routine, and should be able to return from it.

From @smls

On Sun, 20 Jul 2014 10​:29​:57 -0700, masak wrote​:

< masak> r​: sub { sub foo($x = return) { $x }; say foo }(); say "alive"
<camelia> rakudo-jvm bbdcfd​: OUTPUT«alive␤»
<camelia> ..rakudo-moar bbdcfd​: OUTPUT«Attempt to return outside of
any Routine [...]
<camelia> ..rakudo-parrot bbdcfd​: OUTPUT«alive␤Nominal type check
failed for parameter '$x'; expected Any but got Mu instead␤»

This works now with Rakudo MoarVM as well.

  ➜ sub { sub foo($x = return) { $x }; say foo }(); say "alive";
  alive

bisectable6 reports¹ that it was fixed by one of these commits​:

  rakudo/rakudo@e609822
  rakudo/rakudo@615d30c
  rakudo/rakudo@8beb87b
  rakudo/rakudo@05170e0
  rakudo/rakudo@899e0fd
  rakudo/rakudo@e544376
  rakudo/rakudo@fcd0093
  rakudo/rakudo@04929fe
  rakudo/rakudo@7ee6578
  rakudo/rakudo@519e764

Ticket can be closed with tests.

[1] https://gist.github.com/Whateverable/7807d6ff7d2e1d059172c7cb784bd4d7

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

From @zoffixznet

Tests​: Raku/roast@809abcd5a7

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