Skip Menu |
Report information
Id: 130485
Status: new
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: alex.jakimenko [at]

Severity: (no value)
Tag: (no value)
Platform: (no value)
Patch Status: (no value)
VM: (no value)

Subject: » is no longer shuffled (<a b c d>».say)
Download (untitled) / with headers
text/plain 958b
Code: <a b c d>».say Result (2015.07): d b c a Result (HEAD): a b c d 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 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

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at