From: naruse@airemix.jp
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:51009] [Ruby master Bug#17575] deprecated style `respond_to?` warning with `-W:no-deprecated`
Date: Tue, 02 Feb 2021 08:48:52 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-90240.20210202084852.4@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-17575.20210123105650.4@ruby-lang.org>
Issue #17575 has been updated by naruse (Yui NARUSE).
Backport changed from 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: REQUIRED to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONE
ruby_3_0 fb6cb226a03c2eeaf4fe68b282fcd6e4a8696ffd merged revision(s) 8dfae85adb96cf3da84bf38f2103969d4a7aed3f.
----------------------------------------
Bug #17575: deprecated style `respond_to?` warning with `-W:no-deprecated`
https://bugs.ruby-lang.org/issues/17575#change-90240
* Author: nobu (Nobuyoshi Nakada)
* Status: Closed
* Priority: Normal
* Backport: 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONE
----------------------------------------
When `respond_to?` is defined in deprecated style, arity == 1, is warned and the defined location is also reported.
But if deprecation warning is disabled, the main message is disabled but the next line is still shown.
```
$ ruby -W:deprecated -e 'class << (obj = "test"); def respond_to?(m) true; end; def test; defined?(foo); end; end; p obj.test'
-e:1: warning: test.respond_to?(:foo) uses the deprecated method signature, which takes one parameter
-e:1: warning: respond_to? is defined here
"method"
```
```
$ ruby -W:no-deprecated -e 'class << (obj = "test"); def respond_to?(m) true; end; def test; defined?(foo); end; end; p obj.test'
-e:1: warning: respond_to? is defined here
"method"
```
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2021-02-02 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 10:56 [ruby-dev:50995] " nobu
2021-02-02 8:48 ` naruse [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-90240.20210202084852.4@ruby-lang.org \
--to=naruse@airemix.jp \
--cc=ruby-dev@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).