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

Calling fail inside a start block causes weird internal error talking about &Return in Rakudo #3583

Closed
p6rt opened this issue Nov 13, 2014 · 4 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Nov 13, 2014

Migrated from rt.perl.org#123204 (status was 'resolved')

Searchable as RT123204$

@p6rt
Copy link
Author

p6rt commented Nov 13, 2014

From @masak

<PerlJam> $promise.status will tell you Kept/Broken
<PerlJam> (IIRC)
<moritz> m​: my $promise = start { die 42 }; await $promise; say $promise.status
<camelia> rakudo-moar f8f6fe​: OUTPUT«===SORRY!===␤42␤»
<moritz> m​: my $promise = start { fail 42 }; await $promise; say $promise.status
<camelia> rakudo-moar f8f6fe​: OUTPUT«===SORRY!===␤Could not find
symbol '&Return'␤»
<PerlJam> huh
<PerlJam> that second one is surely LTA
<masak> agreed.
<masak> please submit.
<PerlJam> um ... I'm not currently in a state where I can easily
submit a rakudo bug
<masak> PerlJam​: I'll do it.
* masak submits rakudobug

@p6rt
Copy link
Author

p6rt commented Mar 12, 2016

From @moritz

On Thu Nov 13 13​:03​:49 2014, masak wrote​:

<PerlJam> $promise.status will tell you Kept/Broken
<PerlJam> (IIRC)
<moritz> m​: my $promise = start { die 42 }; await $promise; say
$promise.status
<camelia> rakudo-moar f8f6fe​: OUTPUT«===SORRY!===␤42␤»
<moritz> m​: my $promise = start { fail 42 }; await $promise; say
$promise.status
<camelia> rakudo-moar f8f6fe​: OUTPUT«===SORRY!===␤Could not find
symbol '&Return'␤»

It is my pleasure to inform you that this has been fixed in the mean time, and I've added tests with Raku/roast@f87e7b421e

Best regards,
Moritz

@p6rt
Copy link
Author

p6rt commented Mar 12, 2016

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

@p6rt
Copy link
Author

p6rt commented Mar 12, 2016

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

@p6rt p6rt closed this as completed Mar 12, 2016
@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
Labels
Projects
None yet
Development

No branches or pull requests

1 participant