Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LTA error message about returning from an exhausted routine in Rakudo #2823

Open
p6rt opened this issue Jul 8, 2012 · 3 comments
Open

LTA error message about returning from an exhausted routine in Rakudo #2823

p6rt opened this issue Jul 8, 2012 · 3 comments
Labels
Bug

Comments

@p6rt
Copy link

@p6rt p6rt commented Jul 8, 2012

Migrated from rt.perl.org#114042 (status was 'open')

Searchable as RT114042$

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jul 8, 2012

From @masak

<masak> rn​: sub a { my &x = { return }; &x }; my &y = a; &y()
<p6eval> rakudo 138213​: OUTPUT«(timeout)»
<masak> hm, locally on rakudo I get 'Attempt to return outside of any
Routine'. I don't much like that error.
<masak> the return is in a Routine.
<masak> it's just that the Routine in question is exhausted.
<pmichaud> ...a Routine that has already exited, though.
<masak> right, I agree that the return heppens dynamically outside the
dynamic scope of the Routine.
<pmichaud> yes, that seems like a LTA error message
* masak submits rakudobug
<benabik> rn​: sub a { my &x = { return }; &x }; sub b(&x) { &x() }; b(a)
<p6eval> rakudo 138213​: OUTPUT«(timeout)»
<p6eval> ..niecza v19-13-g442e075​: ( no output )
<masak> locally I still get 'Attempt to return outside of any Routine'
<masak> benabik++

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Apr 26, 2016

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

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented May 10, 2018

From @skids

This was fixed on MoarVM for rakudo/rakudo#1216

Tests added for the variants in this ticket in perl6/roast@fe57091

JVM apparently still needs work on this, so the tests are skipped for JVM.

keeping open for JVM fixes.

@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.