From: zzak@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:69890] [Ruby trunk - Bug #11327] Improve duplicate key warning.
Date: Tue, 07 Jul 2015 18:29:22 +0000 [thread overview]
Message-ID: <redmine.journal-53309.20150707182921.88789fd7d1d30446@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11327.20150703193002@ruby-lang.org
Issue #11327 has been updated by Zachary Scott.
If matz will approve, and no objection, I will commit it.
----------------------------------------
Bug #11327: Improve duplicate key warning.
https://bugs.ruby-lang.org/issues/11327#change-53309
* Author: Andre Medeiros
* Status: Open
* Priority: Normal
* Assignee: Zachary Scott
* ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
This change rephrases the duplicate key warning, which causes some confusion.
Before:
~~~
/Users/andre/bug.rb:4: warning: duplicated key at line 5 ignored: :max_instances
~~~
After:
~~~
/Users/andre/bug.rb:4: warning: key :max_instances is duplicated and overwritten on line 5
~~~
---Files--------------------------------
message_fix.diff (647 Bytes)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2015-07-07 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11327.20150703193002@ruby-lang.org>
2015-07-03 19:30 ` [ruby-core:69860] [Ruby trunk - Bug #11327] [Open] Improve duplicate key warning me
2015-07-07 18:29 ` zzak [this message]
2015-07-08 1:59 ` [ruby-core:69896] [Ruby trunk - Bug #11327] " matz
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=redmine.journal-53309.20150707182921.88789fd7d1d30446@ruby-lang.org \
--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).