-
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
Looping over a HyperSeq in sink context does nothing (for <a b c>.hyper { say 2 }) #6435
Comments
From @AlexDanielCode: Result (2015.09-2015.06): Result (9b0b9effe5,2017.07,HEAD(6745517)): There seems to be nothing wrong with using a for loop on .hyper or .race, so it should work. It starts working if you somehow use the value, for example: Code: Result (9b0b9effe5,2017.07,HEAD(6745517)): Bisectable points to rakudo/rakudo@9b0b9ef |
From @AlexDanielIRC discussion: https://irclog.perlgeek.de/perl6/2017-08-09#i_14989886 Turns out that .hyper/.race never worked reliably anyway, so this ticket is less important than it looks. Maybe we should have a meta ticket that tracks all .hyper/.race issues. Another option would be to just close them all, but this will leave us without a good list of tests that should be written. On 2017-08-08 18:40:48, alex.jakimenko@gmail.com wrote:
|
From @jnthnOn Tue, 08 Aug 2017 18:40:48 -0700, alex.jakimenko@gmail.com wrote:
Fixed in new hyper/race implementation; tests in S07-hyperrace/hyper.t and S07-hyperrace/race.t. |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#131865 (status was 'resolved')
Searchable as RT131865$
The text was updated successfully, but these errors were encountered: