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
.Int-ing a non-numeric Str no longer throws, but returns a Failure instead (my $i = 'a'.Int) #5945
Comments
From @AlexDanielCode: Result (2015.12, 2016.03): Actually thrown at: Result (HEAD): So instead of throwing it just gives a Failure object. Bisectable points to rakudo/rakudo@1cb2e8d I find the current behavior a bit surprising, but feel free to argue with that. |
From @lizmatTo me, that’s ENOTABUG, because that’s exactly what fail / Failure is supposed to do. Only when you actually *use* the value unprotected, will it throw. # protected usage # unprotected usage The commit fixes behaviour.
|
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielYou are right. This is not a regression, but we still need some tests for this I think. On 2016-12-30 02:23:30, elizabeth wrote:
|
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130450 (status was 'resolved')
Searchable as RT130450$
The text was updated successfully, but these errors were encountered: