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
» is no longer shuffled (<a b c d>».say) #5967
Comments
From @AlexDanielCode: Result (2015.07): Result (HEAD): The idea was that the order of processing is not defined for » (though the results are returned in order), therefore it is a good idea to shuffle the results a little bit so that the user is not going to assume that » works like .map Bisectable points to rakudo/rakudo@a519305 The commit description does not identify why the previous behavior was removed. Is it for performance reasons? Or did it just slip through the cracks? Anyway, it would be nice to make it process things in some weird order. If the performance is such a big concern, then perhaps processing just one element (e.g. the first one) in a different order (as last) will probably save the problem for users yet won't introduce a noticeable performance hit. This is part of a much larger discussion. See also Raku/doc#1107 |
From @AlexDaniel<Zoffix> AlexDaniel: FWIW jnthn++ said we'll likely make ». autothread only is pure routines, so no shuffling is really needed On 2017-01-02 11:31:47, alex.jakimenko@gmail.com wrote:
|
From @AlexDaniel<AlexDaniel_> Zoffix: so <a b c d>».say should not be discouraged? Interesting On 2017-10-07 09:32:43, alex.jakimenko@gmail.com wrote:
|
From @AlexDaniel<TimToady> » is supposed to be an explicit promise that you don't care about order, and there are lots of places that are not marked pure that are nevertheless effectively pure On 2017-10-07 09:34:59, alex.jakimenko@gmail.com wrote:
|
From @zoffixznetOn Sat, 07 Oct 2017 09:38:10 -0700, alex.jakimenko@gmail.com wrote:
More details on this: We actually still fake-shuffle non-nodal hypers, because those we handle with &nodemap, Both are bit underspecced[^1] but looks like this Issue goes beyond just shuffling results $ ./perl6 -e '(lazy <a b c>)».uc' $ ./perl6 -e '(lazy <a b c>)».elems' $ ./perl6 -v [1] Raku/roast#370 |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#130485 (status was 'open')
Searchable as RT130485$
The text was updated successfully, but these errors were encountered: