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
List declarations of lexicals with native types blows up #2540
Comments
From @moritz12:07 < moritz> nom: my int ($x, $y); |
From @masak<masak> std: my int ($a, $b) All the declarations above should either Just Work, or throw a better The strange error messages above seem specific to native types, but <masak> nom: my (Int $a); $a = "OH HAI"; say 'alive' Declaring a type the normal way works, of course. <masak> nom: my Int $a; $a = "OH HAI"; say 'alive' Having the type declarations within parentheses mean nothing violates |
From @usev6skids++ added some tests for this ticket to roast: Raku/roast@b354a9304f The declarations with native types don't blow up any longer -- e.g. $ perl6-j -e 'my (int $a); say "alive"' The type constraints within the signatures don't work, though: $ perl6-m -e 'my (Int $a); $a = "foo"; say "alive"' $ perl6-m -e 'my (int $a); $a = "foo"; say "alive"' |
1 similar comment
From @usev6skids++ added some tests for this ticket to roast: Raku/roast@b354a9304f The declarations with native types don't blow up any longer -- e.g. $ perl6-j -e 'my (int $a); say "alive"' The type constraints within the signatures don't work, though: $ perl6-m -e 'my (Int $a); $a = "foo"; say "alive"' $ perl6-m -e 'my (int $a); $a = "foo"; say "alive"' |
@usev6 - Status changed from 'new' to 'open' |
From @jnthnOn Sun Mar 01 12:22:34 2015, bartolin@gmx.de wrote:
Fixed these now, unfudged the tests in S04-declarations/my.t, and written some extra tests to give better coverage. |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#102414 (status was 'resolved')
Searchable as RT102414$
The text was updated successfully, but these errors were encountered: