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
random hash order in .perl method on Moar and JVM #3751
Comments
From @dwarringThe perl method on Rakudo/MoarVM currently outputs has entries in a random order: % perl6-m -e'say { :a(10), :b(20), :c(30) }.perl' JVM otoh, does seem to order consistantly: % perl6-j -e'say { :a(10), :b(20), :c(30) }.perl' S02 doesn't have an opinion on hash ordering - http://design.perl6.org/S02.html#The_.perl_method I'm in the habit of using the .perl method as part of the normal development/debugging progress, but I find that the MoarVM behavior can be a bit taxing in practice. Could the MoarVM .perl method also order hash entries? |
From @dwarringCorrection: both MoarVM and JVM are re-ordering hash entries. Changing the title of this ticket.
|
From @pmichaudOn Sun Mar 22 13:04:21 2015, david.warring wrote:
Requiring .perl to order hash entries ought to be a language/specification change, rather than something that individual compilers do on their own. Otherwise programmers may falsely rely on a compiler-specific behavior. To have this considered as a language feature, add an issue to GitHub: https://github.com/perl6/specs/issues Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @dwarringOn Mon Mar 23 06:48:38 2015, pmichaud wrote:
Have opened issue Raku/old-design-docs#88 |
From @dwarringThe .perl method on Hashes has been reworked in the latest rakudo. Looks good! (Looks Good!!). % perl6-m --version Hashes currently appear to be ordered. On Mon Mar 23 11:09:33 2015, david.warring wrote:
|
From @cokeOn Sun May 10 13:20:24 2015, david.warring wrote:
.perl on hashes is now sorted - all the tests in S32-hash/perl.t implicitly cover this condition. Resolving ticket. |
@coke - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#124148 (status was 'resolved')
Searchable as RT124148$
The text was updated successfully, but these errors were encountered: