Feature #994


Hash-order preservation should be declared a feature; documentation needs to be adapted

Added by JWuttke (Joachim Wuttke) over 13 years ago. Updated over 11 years ago.

Target version:


I would like to come back to a thread from March 2008 in comp.lang.ruby,

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."

Actions #1

Updated by ko1 (Koichi Sasada) over 13 years ago

  • Assignee set to matz (Yukihiro Matsumoto)



Actions #2

Updated by marcandre (Marc-Andre Lafortune) about 13 years ago

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



Actions #3

Updated by marcandre (Marc-Andre Lafortune) about 13 years ago

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

Applied in changeset r25081.


Also available in: Atom PDF