From @masak

<masak> rakudo​: .say for 1, 2, 4 ... 256
<p6eval> rakudo fc57d1​: OUTPUT«1␤2␤4␤8␤16␤32␤64␤128␤256␤»
<cotto> rakudo​: .say for 1, 2, 6 ... 33.4
<p6eval> rakudo fc57d1​: OUTPUT«Attempt to return from exhausted Routine [...]
<JimmyZ> rakudo​: .say for 1, 2, 11 ... 256
<p6eval> rakudo fc57d1​: OUTPUT«Attempt to return from exhausted Routine [...]
<cotto> lulz
* masak submits rakudobug
<masak> cotto++

Surely there could be a more informative/pertinent error message than
"exhausted Routine" in this case? :-) We all know calculating
sequences is very tiring, but...

From @masak

On Thu Sep 08 00​:35​:23 2011, masak wrote​:

<masak> rakudo​: .say for 1, 2, 4 ... 256
<p6eval> rakudo fc57d1​: OUTPUT«1␤2␤4␤8␤16␤32␤64␤128␤256␤»
<cotto> rakudo​: .say for 1, 2, 6 ... 33.4
<p6eval> rakudo fc57d1​: OUTPUT«Attempt to return from exhausted
Routine [...]
<JimmyZ> rakudo​: .say for 1, 2, 11 ... 256
<p6eval> rakudo fc57d1​: OUTPUT«Attempt to return from exhausted
Routine [...]
<cotto> lulz
* masak submits rakudobug
<masak> cotto++

Surely there could be a more informative/pertinent error message than
"exhausted Routine" in this case? :-) We all know calculating
sequences is very tiring, but...

<pmichaud> I wonder if RT 98678 is a problem with return/fail inside of
a gather.
<pmichaud> rakudo​: sub xyz() { gather { take 1; return 2; take 3; } };
say xyz();
<p6eval> rakudo fc57d1​: OUTPUT«Attempt to return from exhausted Routine
[...]
<masak> so... exhausting!
<pmichaud> rakudo​: sub xyz() { gather { take 1; fail 2; take 3; } };
say xyz();
<p6eval> rakudo fc57d1​: OUTPUT«Attempt to return from exhausted Routine
[...]
<pmichaud> yup, that's the problem.
* masak adds this to the ticket

@masak - Status changed from 'new' to 'open'

From @pmichaud

Now fixed in (nom) 5d26134. Need a spectest and then we can close this
ticket.

Pm

From @moritz

tested in S32-exceptions/misc.t

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