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
Assigning Failure to typed variable swallows Failure information #4661
Comments
From carsten.hartenfels@googlemail.comThis bug is for Rakudo version 2015.09-419-gfae01fb built on MoarVM The following code, in `t.pl`: sub s { fail 'important failure message' } will output: Type check failed in assignment to $x; expected Int but got Failure But it omits the important failure message, as well as where it was sub s { fail 'important failure message' } will output the much more useful message: important failure message Actually thrown at: This seems to make typed variables much less useful, since they Ideally, the type check message would include the failure information Type check failed in assignment to $x; expected Int but got Failure |
From @lizmatFixed with a31cc91a0d604a8a74529 . Tests are still needed
|
The RT System itself - Status changed from 'new' to 'open' |
From @TimToadyOn Mon Oct 19 07:02:44 2015, elizabeth wrote:
The existing 'method priors' wasn't working correctly due to a precedence error originally made by TimToady-- that ate the priors result as part of the ??!! conditional. Simply adding a "do" fixes that and renders the previous patch unnecessary. Fixed in 48a0888cced2e772d9b347460a69507fc822bd2d (tests still needed). |
1 similar comment
From @TimToadyOn Mon Oct 19 07:02:44 2015, elizabeth wrote:
The existing 'method priors' wasn't working correctly due to a precedence error originally made by TimToady-- that ate the priors result as part of the ??!! conditional. Simply adding a "do" fixes that and renders the previous patch unnecessary. Fixed in 48a0888cced2e772d9b347460a69507fc822bd2d (tests still needed). |
From @AlexDanieljmerelo++, tests added in Raku/roast@ce173d4 Closing On 2015-10-19 07:43:11, larry wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126394 (status was 'resolved')
Searchable as RT126394$
The text was updated successfully, but these errors were encountered: