Bug #21641: Hash#to_s behaves different in 3.4

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN

[matheussilvasantos (Matheus Oliveira)]

I couldn't find anywhere documenting this change from Ruby 3.3 to Ruby 3.4:

3.3.9:

> irb
3.3.9 :001 > {x:1}.to_s
 => "{:x=>1}" 
3.3.9 :002 >

3.4.0:

3.4.0 :001 > {x:1}.to_s
 => "{x: 1}" 
3.4.0 :002 > 

Is there a way to continue with the old behaviour - flag to compilation, monkey patch, etc.?

Unfortunately, the application I'm working on stores the to_s in Redis and use it later; if the result doesn't match for the same Hash, it would break a few things.

[masterleep2 (Bill Lipa)]

It's mentioned in https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-0-released/ under Hash#inspect rendering have been changed. [Bug #20433]

[shan (Shannon Skipper)]

Please feel free to join us on Ruby Discord or #ruby IRC to discuss all the options! Refining Hash is one way:

module LegacyHashToS
  refine Hash do
    def to_s = "{#{map { "#{_1.inspect}=>#{_2.inspect}" }.join(', ')}}"
  end
end

using LegacyHashToS

{x: 1}.to_s
#=> "{:x=>1}"

[zenspider (Ryan Davis)]

• Status changed from Open to Closed

closed by request of OP