Bug #20982: Inconsistency between Hash#inspect and ENV.inspect in Ruby 3.4

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE

[herwin (Herwin W)]

Ruby 3.4 changed the stringified output of Hash to add whitespace to the hashrockets

ruby -e 'p({"a"=>"b"})'
{"a" => "b"}

The output of ENV.inspect is very similar to Hash#inspect, but does not include the whitespace

ruby -e 'p ENV'
{"SHELL"=>"/bin/bash", [...] }

Adding the extra whitespace around the hashrockets would improve the readability, and make things more consistent.

[nobu (Nobuyoshi Nakada)]

• Tracker changed from Feature to Bug
• Backport set to 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset commit:git|c6dbb10b7408cab17f170f0b23d1bbf0db03ad55.

---

[Bug #20982] Put spaces in ENV.inspect results as well as Hash

[k0kubun (Takashi Kokubun)]

Cherry-picking commit:c6dbb10b7408cab17f170f0b23d1bbf0db03ad55 to ruby_3_4 caused a conflict. Could you file a PR that resolves it?

[k0kubun (Takashi Kokubun)]

• Backport changed from 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED to 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE

ruby_3_4 commit:24f48c83e7e851a6ca712fc7b498634da9a24789.

[k0kubun (Takashi Kokubun)]

Thanks for the PR.