Skip to content
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

Lazy list in hash loses contents #3280

Closed
p6rt opened this issue Nov 23, 2013 · 6 comments
Closed

Lazy list in hash loses contents #3280

p6rt opened this issue Nov 23, 2013 · 6 comments

Comments

@p6rt
Copy link

p6rt commented Nov 23, 2013

Migrated from rt.perl.org#120620 (status was 'resolved')

Searchable as RT120620$

@p6rt
Copy link
Author

p6rt commented Nov 23, 2013

From cyberuniverses@gmail.com

under Rakudo Star 2013.10​:

say [foo => (1,2,3).map​: {$_}].perl
  #right​: ["foo" => (1, 2, 3).list.item]

say {foo => (1,2,3).map​: {$_}}.perl
  #wrong​: {"foo" => ().list.item}

As this was discovered as a test failure in JSON​::Unmarshal, it seems
likely to be a regression in the August to October range.

@p6rt
Copy link
Author

p6rt commented Oct 11, 2014

From @pmichaud

As of 2014.10.10 this now appears to be working​:

  01​:44 <pmichaud> r​: say {foo => (1,2,3).map​: {$_}}.perl
  01​:44 <camelia> rakudo-{parrot,moar} fd017a​: OUTPUT«{"foo" => (1, 2, 3).list.item}␤»

I think the ticket can be marked as resolved with an appropriate test.

Pm

@p6rt
Copy link
Author

p6rt commented Oct 11, 2014

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Feb 7, 2015

From @usev6

I added test to S32-list/map.t with commit Raku/roast@4eb80b2d48

In case that test is not appropriate, please reopen the ticket (or change the test).

1 similar comment
@p6rt
Copy link
Author

p6rt commented Feb 7, 2015

From @usev6

I added test to S32-list/map.t with commit Raku/roast@4eb80b2d48

In case that test is not appropriate, please reopen the ticket (or change the test).

@p6rt p6rt closed this as completed Feb 7, 2015
@p6rt
Copy link
Author

p6rt commented Feb 7, 2015

@usev6 - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant