Parenthesized for
loop is eager, even with lazy
keyword
#6007
Comments
From @smls ➜ say (for ^4 { .say }).WHAT; ➜ say (lazy for ^4 { .say }).WHAT; I would have expected an output of just `(Seq)` in both cases, or at The synopses don't seem to make a statement on whether a `List` or lazy loops can be indicated by putting the loop in parens (... if COND for LIST) # lazy list comprehension or by use of either a statement prefix or a phaser in lazy for LIST { ... } According to bisectable and committable This is Rakudo version 2016.12-315-gdaf7e5185 built on MoarVM version |
From @smlsThis bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 |
From @dogbert17On Sat, 26 Aug 2017 05:15:41 -0700, smls75@gmail.com wrote:
As per commit rakudo/rakudo@cf1673d |
The RT System itself - Status changed from 'new' to 'open' |
From @dogbert17On Sun, 12 May 2019 07:36:16 -0700, jan-olof.hendig@bredband.net wrote:
As for the first case, see https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2019-05-12#l48 should be set to testneeded |
From @usev6Back in 2017 jnthn++ already added a test for lazy for loops with Raku/roast@3659ede. Since the evaluations in this ticket also take the type into considerations, I've added a new test to S32-list/seq.t with Raku/roast@207171b I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6Back in 2017 jnthn++ already added a test for lazy for loops with Raku/roast@3659ede. Since the evaluations in this ticket also take the type into considerations, I've added a new test to S32-list/seq.t with Raku/roast@207171b I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130572 (status was 'resolved')
Searchable as RT130572$
The text was updated successfully, but these errors were encountered: