From: "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "k0kubun (Takashi Kokubun)" <noreply@ruby-lang.org>
Subject: [ruby-core:121039] [Ruby master Bug#20982] Inconsistency between Hash#inspect and ENV.inspect in Ruby 3.4
Date: Fri, 14 Feb 2025 05:44:34 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-111947.20250214054434.10671@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20982.20241225151722.10671@ruby-lang.org>
Issue #20982 has been updated by k0kubun (Takashi Kokubun).
Thanks for the PR.
----------------------------------------
Bug #20982: Inconsistency between Hash#inspect and ENV.inspect in Ruby 3.4
https://bugs.ruby-lang.org/issues/20982#change-111947
* Author: herwin (Herwin W)
* Status: Closed
* Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
prev parent reply other threads:[~2025-02-14 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 15:17 [ruby-core:120409] [Ruby master Feature#20982] " herwin (Herwin W) via ruby-core
2025-02-14 1:49 ` [ruby-core:121002] [Ruby master Bug#20982] " k0kubun (Takashi Kokubun) via ruby-core
2025-02-14 5:44 ` [ruby-core:121038] " k0kubun (Takashi Kokubun) via ruby-core
2025-02-14 5:44 ` k0kubun (Takashi Kokubun) via ruby-core [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-111947.20250214054434.10671@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).