Feature #994: Hash-order preservation should be declared a feature; documentation needs to be adapted

• Status: Closed
• Assignee: matz (Yukihiro Matsumoto)
• Target version: 1.9.2

[JWuttke (Joachim Wuttke)]

=begin
I would like to come back to a thread from March 2008 in comp.lang.ruby,
http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/5803482840ed66ca/7af75e86b1975224?hl=enaf75e86b1975224:

For me, hash order preservation is an important advantage of Ruby 1.9; it allows me to generate human-readable YAML output without ugly workarounds.

Matz said, it is now a guaranteed feature of CRuby; but at that time he was still cautious regarding Ruby-the-language. Maybe time has come to establish a consensus and to take a decision. It would give me security for the future of my code base.

Once hash-order preservation is declared a feature, the following text in ri1.9 needs to be adapted:
"The order in which you traverse a hash by either key or value may seem arbitrary, and will generally not be in the insertion order."
=end

[ko1 (Koichi Sasada)]

• Assignee set to matz (Yukihiro Matsumoto)

=begin

=end

[marcandre (Marc-Andre Lafortune)]

• Category set to core
• Status changed from Open to Assigned
• Target version set to 1.9.2

=begin

=end

[marcandre (Marc-Andre Lafortune)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

=begin
Applied in changeset r25081.
=end