From: Joseph Jones <joeyi5216@gmail.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Cc: <ruby-core@ruby-lang.org>
Subject: [ruby-core:72332] [Ruby trunk - Bug #11802] [Open] Hash.new and {} have different behaviour
Date: Thu, 17 Dec 2015 21:13:07 -0700 [thread overview]
Message-ID: <23ECEED8-5367-4713-A081-76DF8A006726@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
Joseph Jones liked your message with Boxer. On December 10, 2015 at 08:26:40 MST, aufi.cz@gmail.com wrote:Issue #11802 has been reported by Marek Aufart.----------------------------------------Bug #11802: Hash.new and {} have different behaviourhttps://bugs.ruby-lang.org/issues/11802* Author: Marek Aufart* Status: Open* Priority: Normal* Assignee: * ruby -v: ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux]* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN----------------------------------------It looks that {} is not recognized as a variable sometimes.irb(main):001:0> p Hash.new{}=> {}irb(main):002:0> p {}=> nilSimilar in rspec test:expect(subject.something).to eq {} # fails on not given argument for eqexpect(subject.something).to eq({}) # works-- https://bugs.ruby-lang.org/
[-- Attachment #2: Type: text/html, Size: 1226 bytes --]
reply other threads:[~2015-12-18 3:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23ECEED8-5367-4713-A081-76DF8A006726@gmail.com \
--to=ruby-core@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 read-only IMAP folder(s) and NNTP newsgroup(s).