From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:100360] [Ruby master Bug#17259] Kernel#warn should ignore <internal: entries
Date: Sat, 10 Oct 2020 18:24:36 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-87971.20201010182435.772@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17259.20201010132911.772@ruby-lang.org
Issue #17259 has been updated by jeremyevans0 (Jeremy Evans).
I agree with removing the Rubygems override of `Kernel#warn` (the only Kernel method Rubygems should override is `require`). Skipping `<internal:` entries for `uplevel` makes sense to me.
----------------------------------------
Bug #17259: Kernel#warn should ignore <internal: entries
https://bugs.ruby-lang.org/issues/17259#change-87971
* Author: Eregon (Benoit Daloze)
* Status: Open
* Priority: Normal
* Target version: 3.0
* ruby -v: ruby 3.0.0preview1 (2020-09-25 master 0096d2b895) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
`Kernel#warn` currently does not skip `<internal:` entries from core library methods defined in Ruby.
This can cause rather unhelpful locations to be used for warnings.
For instance:
```
$ ruby -v --disable=gems -e 'def deprecated; warn "use X instead", uplevel: 1; end; tap(&:deprecated)'
ruby 3.0.0preview1 (2020-09-25 master 0096d2b895) [x86_64-linux]
<internal:kernel>:90: warning: use X instead
# expected: "-e:1: warning: use X instead"
```
Note that RubyGems overrides Kernel#warn since https://github.com/rubygems/rubygems/pull/2442 and https://github.com/rubygems/rubygems/blob/c1bafab1d84e0aad06e377e9db4b74cccab4b43a/lib/rubygems/core_ext/kernel_warn.rb#L42,
so `--disable-gems` is needed to observe this behavior.
I think it is very suboptimal that RubyGems needs to monkey-patch Kernel#warn to remove RubyGems' `require` from `Kernel#warn` location.
That is both fragile (as we've seen from various incompatible behavior and bugs in that monkey-patch) and inefficient (walking the stack multiple times).
So I would suggest to actually skip all backtraces entries starting with `<internal:` for `Kernel#warn(message, uplevel:)`.
BTW this is already what [TruffleRuby does](https://github.com/oracle/truffleruby/blob/c3bcccfd8db7d460e23f0371e7ceaf5fdb71275c/src/main/ruby/truffleruby/core/kernel.rb#L656).
As a bonus, by filtering out `<internal:`, RubyGems could define its `require` in an `eval(code, nil, '<internal:rubygems-require>', line)` and it would automatically be skipped, without needing to monkey-patch Kernel#warn at all!
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2020-10-10 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 13:29 [ruby-core:100357] [Ruby master Bug#17259] Kernel#warn should ignore <internal: entries eregontp
2020-10-10 18:24 ` merch-redmine [this message]
2020-10-11 2:43 ` [ruby-core:100362] " nobu
2020-10-11 10:23 ` [ruby-core:100370] " eregontp
2020-10-13 18:21 ` [ruby-core:100397] [Ruby master Feature#17259] " eregontp
2020-10-26 5:27 ` [ruby-core:100553] " matz
2020-11-20 18:27 ` [ruby-core:100987] " eregontp
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-87971.20201010182435.772@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).