-
Notifications
You must be signed in to change notification settings - Fork 1
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
Internal error message on Z=> in enum declaration in Rakudo #3049
Comments
From @masak<TimToady> r: enum Color (<red green purple> Z=> 1,2,4); |
From @usev6This command no longer results in an internal error message. But the resulting enum is not what I expected in the first place (but maybe it's technically correct): $ perl6 -e 'enum Color (<red green purple> Z=> 1,2,4); say Color.enums' I get the same result when I add an extra pair of parens around a list of pairs: $ perl6 -e 'enum Color (red => 1, green => 2, purple => 4); say Color.enums' $ perl6 -e 'enum Color ((red => 1, green => 2, purple => 4)); say Color.enums' But I cannot just remove the parens in the first example since, since that seems to execute 'enum Color <red green purple' and zip the resulting enum with (1, 2, 4): $ perl6 -e 'say enum Color <red green purple> Z=> 1,2,4; say Color.enums' |
1 similar comment
From @usev6This command no longer results in an internal error message. But the resulting enum is not what I expected in the first place (but maybe it's technically correct): $ perl6 -e 'enum Color (<red green purple> Z=> 1,2,4); say Color.enums' I get the same result when I add an extra pair of parens around a list of pairs: $ perl6 -e 'enum Color (red => 1, green => 2, purple => 4); say Color.enums' $ perl6 -e 'enum Color ((red => 1, green => 2, purple => 4)); say Color.enums' But I cannot just remove the parens in the first example since, since that seems to execute 'enum Color <red green purple' and zip the resulting enum with (1, 2, 4): $ perl6 -e 'say enum Color <red green purple> Z=> 1,2,4; say Color.enums' |
@usev6 - Status changed from 'new' to 'open' |
From @AlexDanielYeah, this is not correct, and it was resolved in (2017-11-27) rakudo/rakudo@d9021cf Now you may wonder when the original “Method 'returns' not found” was fixed, and… that was on Parrot :) So not really bisectable and not even relevant today. W4anD0eR96++ wrote a test for it in Raku/roast@1fbabe9 Closing. On 2015-01-06 13:51:00, bartolin@gmx.de wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#116719 (status was 'resolved')
Searchable as RT116719$
The text was updated successfully, but these errors were encountered: