[ruby-core:115231] [Ruby master Feature#19985] Support `Pathname` for `require`

Issue #19985 has been updated by zverok (Victor Shepelev).


> That's not funny, it's expected, as load deals exclusively with paths, and require does not generally deal with paths. 

Yeah, makes sense. 

> But in general, require does not deal with paths. I don't think we should add Pathname support to require.

Makes sense. Then, probably, it is up to RubyGems to remove this false conversion.

----------------------------------------
Feature #19985: Support `Pathname` for `require`
https://bugs.ruby-lang.org/issues/19985#change-105147

* Author: vo.x (Vit Ondruch)
* Status: Open
* Priority: Normal
----------------------------------------
It seems that RubyGems / Bundler `require` method overrides of accept `Pathname` as and argument

~~~
$ ruby -rpathname -e '
pa = Pathname.new("test")
require pa
'
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- test (LoadError)
	from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from -e:3:in `<main>'
~~~

while plain Ruby require does not:

~~~
$ ruby --disable-gems -rpathname -e '
pa = Pathname.new("test")
require pa
'
-e:3:in `require': no implicit conversion of Pathname into String (TypeError)
	from -e:3:in `<main>'
~~~

This inconsistency is surprising. It seems that RubyGems / Bundler developers think [1] that Ruby `require` should also accept `Pathname`.

~~~
$ ruby -v
ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux]
~~~
[1]: https://github.com/rubygems/rubygems/pull/7128



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/