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
Match objects don't roundtrip through .perl #4282
Comments
From @cokeThere's a failing test in S05-match/perl.t for this. Looks like the topmost "hash" attribute isn't the same. # expected: Match.new(ast => Any, list => (), hash => -- |
From @cokeAdditionally, there's a test that refers to <operator> on the match object, which dies with: This representation (Null) does not support associative access That is skipped. -- |
1 similar comment
From @cokeAdditionally, there's a test that refers to <operator> on the match object, which dies with: This representation (Null) does not support associative access That is skipped. -- |
From @usev6As far as I understand it, the problem can be golfed to the following: $ perl6 -e 'say EnumMap.new("a", 42).perl' $ perl6 -e 'say EnumMap.new("a", 42).perl.perl' $ perl6 -e 'say EnumMap.new("a", 42).perl.EVAL' |
1 similar comment
From @usev6As far as I understand it, the problem can be golfed to the following: $ perl6 -e 'say EnumMap.new("a", 42).perl' $ perl6 -e 'say EnumMap.new("a", 42).perl.perl' $ perl6 -e 'say EnumMap.new("a", 42).perl.EVAL' |
@usev6 - Status changed from 'new' to 'open' |
From @lizmat
FWIW, PairMap currently suffers the same issue. And Hash would as well, if TimToday hadn’t implemented the new <> decont notation and then change the .perl output to using {}. :-( Not sure whether to fix .new on these, the underlying STORE, or .perl. Liz |
From @usev6The tests in question have been unfudged with roast commit Raku/roast@6db316eaae. (This was probably fixed with merging the 'uncurse' branch.) The last example from the last comment (using EVAL) works as expected, too: $ ./perl6-m -e 'say Map.new("a", 42).perl.EVAL' I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6The tests in question have been unfudged with roast commit Raku/roast@6db316eaae. (This was probably fixed with merging the 'uncurse' branch.) The last example from the last comment (using EVAL) works as expected, too: $ ./perl6-m -e 'say Map.new("a", 42).perl.EVAL' I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125293 (status was 'resolved')
Searchable as RT125293$
The text was updated successfully, but these errors were encountered: