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
A caught exception still exits a sub ? #4809
Comments
From @lizmat[01:02:33] <lizmat> m: sub a($a) { $a(); CATCH { default { say "default" } }; 42 }; say a( -> { die } ) # shorter version This is the cause of the failure in t/spec/S17-scheduler/at.t |
From @TimToadyThe default of die is to, er, die. You can resume after a die, but only if you do so explicitly, in which case you are responsible for overriding the expectations of whoever wrote the die and likely did not expect it to return.
Here's the problem with that:
Okay so far, but suppose we violate the invariant...
So resuming is never going to be the default for die. (That's why we have warn, after all.) |
The RT System itself - Status changed from 'new' to 'open' |
@TimToady - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#126789 (status was 'rejected')
Searchable as RT126789$
The text was updated successfully, but these errors were encountered: