From: eregontp@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92986] [Ruby trunk Feature#15903] Move RubyVM.resolve_feature_path to Kernel.resolve_feature_path
Date: Wed, 05 Jun 2019 20:13:51 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15903.20190605201351.e9b6d21be5362420@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15903.20190605201351@ruby-lang.org
Issue #15903 has been reported by Eregon (Benoit Daloze).
----------------------------------------
Feature #15903: Move RubyVM.resolve_feature_path to Kernel.resolve_feature_path
https://bugs.ruby-lang.org/issues/15903
* Author: Eregon (Benoit Daloze)
* Status: Open
* Priority: Normal
* Assignee:
* Target version: 2.7
----------------------------------------
RubyVM contains mostly MRI-specific features but `resolve_feature_path` is clearly not MRI-specific.
So I propose to move it as a class method of `Kernel`.
I think this makes sense given the related `load` and `require` are defined in `Kernel` too.
Moreover, moving this method outside `RubyVM` is *necessary* for other Ruby implementations to implement it, and keep the clean separation that `RubyVM` is only defined on MRI (see #15752).
So, can I move `RubyVM.resolve_feature_path` to `Kernel.resolve_feature_path`?
Do we need to keep the method on RubyVM (and deprecate it), or can we just remove it since anyway API under RubyVM is not stable?
cc @mame
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-06-05 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15903.20190605201351@ruby-lang.org>
2019-06-05 20:13 ` eregontp [this message]
2019-06-05 20:17 ` [ruby-core:92987] [Ruby trunk Feature#15903] Move RubyVM.resolve_feature_path to Kernel.resolve_feature_path eregontp
2019-06-05 22:51 ` [ruby-core:92989] " jean.boussier
2019-06-05 23:11 ` [ruby-core:92991] " mame
2019-06-06 9:17 ` [ruby-core:93000] " eregontp
2019-06-06 9:18 ` [ruby-core:93001] " eregontp
2019-06-06 9:25 ` [ruby-core:93002] " eregontp
2019-06-06 9:59 ` [ruby-core:93007] " mame
2019-06-13 8:24 ` [ruby-core:93097] " nobu
2019-06-13 9:33 ` [ruby-core:93101] " eregontp
2019-06-14 2:51 ` [ruby-core:93123] " mame
2019-06-14 21:45 ` [ruby-core:93148] " eregontp
2019-07-11 4:53 ` [ruby-core:93660] [Ruby master " matz
2019-07-13 10:37 ` [ruby-core:93740] " eregontp
2019-07-13 13:37 ` [ruby-core:93741] " 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.issue-15903.20190605201351.e9b6d21be5362420@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).