Feature #4233


autoload Can't Require Gems

Added by runpaint (Run Paint Run Run) over 12 years ago. Updated almost 6 years ago.

Target version:


Is it intentional that when used via autoload, require can't handle Gem names?

 run@desktop:~/mir/ruby$  →  ruby -e 'p require "nokogiri"'
 run@desktop:~/mir/ruby$  →  ruby -e 'autoload(:N, "nokogiri"); p N'
 -e:1:in `<main>': cannot load such file -- nokogiri (LoadError)


Actions #1

Updated by naruse (Yui NARUSE) over 12 years ago

  • Status changed from Open to Assigned
  • Assignee set to nahi (Hiroshi Nakamura)
  • Target version set to 2.0.0
Actions #2

Updated by nahi (Hiroshi Nakamura) about 11 years ago

  • Tracker changed from Bug to Feature

Updated by mame (Yusuke Endoh) almost 11 years ago

  • Assignee changed from nahi (Hiroshi Nakamura) to drbrain (Eric Hodel)

Is this really a feature request? Looks a (low-priority?) bug to me.
drbrain, what do you think about this?

Yusuke Endoh

Updated by drbrain (Eric Hodel) almost 11 years ago

  • Assignee changed from drbrain (Eric Hodel) to nahi (Hiroshi Nakamura)

If I'm reading load.c correctly, autoload_provided() uses rb_feature_provided() which checks $LOAD_PATH only. This will cause autoload to fail if the gem has not been activated yet.

If autoload's specification only allows autoloading from $LOAD_PATH this is not a bug. The documentation for Kernel#autoload does not say how the file will be loaded, but Module#autoload says:

Registers filename to be loaded (using Kernel::require) the first
time that module (which may be a String or a symbol) is accessed
in the namespace of mod.

Which implies it is a bug. Perhaps this documentation is wrong.

Since nahi is the autoload expert, I have assigned this back to him.


Updated by mame (Yusuke Endoh) almost 11 years ago

  • Target version changed from 2.0.0 to 2.6

Thank you drbrain for the explanation!
Recently, nahi is not so active. So, I'm sorry but I recognize this as a (bad) spec of 2.0.0.

Yusuke Endoh

Updated by mame (Yusuke Endoh) almost 6 years ago

  • Status changed from Assigned to Closed

Seems this issue was fixed. Closing.


Also available in: Atom PDF