Project

General

Profile

Actions

Feature #15903

closed

Move RubyVM.resolve_feature_path to Kernel.resolve_feature_path

Added by Eregon (Benoit Daloze) about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
[ruby-core:92986]

Description

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 (Yusuke Endoh)


Related issues 2 (0 open2 closed)

Related to Ruby master - Feature #15230: RubyVM.resolve_feature_pathClosedmatz (Yukihiro Matsumoto)Actions
Related to Ruby master - Feature #15752: A dedicated module for experimental featuresFeedbackActions
Actions

Also available in: Atom PDF