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
Rakudo doesn't build pairs correctly for :foo[...], :foo<...>, :foo{...} #1103
Comments
From @masak<masak> rakudo: my $a = :x[] |
From @pmichaudOn Fri Jun 26 07:56:40 2009, masak wrote:
What should $a contain in the above case? I.e., what's the Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @moritzPatrick R. Michaud via RT wrote:
I think it should be the same as my $a = x => []; (that is a pair holding an empty list or array, don't know exactly which). cheers, |
From @masak<masak> rakudo: :a() |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/t/spec/S02-builtin_data_types/pair.t |
The RT System itself - Status changed from 'new' to 'open' |
From @masak<masak> rakudo: my $x = bar => [ baz => 42, sloth => 43 ]; my $y = |
From @moritzOn Sun Aug 09 14:31:17 2009, masak wrote:
... but it seems to be unrelated to that move. I unrolled these commits locally: Then recompiled and ran the new tests, that didn't change anything. It seems that the :foo[...] colonpair syntax doesn't set up the array # correct: one iteration: # flat list, two iterations (IMHO wrong): as I understand .value it should return a scalar, not a list. Cheers, |
The RT System itself - Status changed from 'new' to 'open' |
From @pmichaudOn Sun Aug 09 14:56:24 2009, moritz wrote:
Correct, Rakudo doesn't handle the non-paren colonpair syntaxes yet Pm |
From @moritzSeems to work now... leaving open to ensure test coverage |
From @moritzCarl MXXsak (via RT) wrote:
You can now find passing tests in S02-literals/pairs.t. |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#66996 (status was 'resolved')
Searchable as RT66996$
The text was updated successfully, but these errors were encountered: