Issue #21154 has been updated by akr (Akira Tanaka). autoload is virtual require. (like virtual memory) In general, a user of require or autoload expects the specified library is usable after require or autoload. However, it is not hold when a user invokes require or autoload a library currently loading. It is simply impossible. It is nice to document it and applications does not depend the autoload behavior in the situation. I think it is possible to avoid that by checking caller_locations. ---------------------------------------- Misc #21154: Document or change Module#autoload? https://bugs.ruby-lang.org/issues/21154#change-112722 * Author: fxn (Xavier Noria) * Status: Feedback * Assignee: mame (Yusuke Endoh) ---------------------------------------- The documentation of `Module#autoload?` says
Returns filename to be loaded if name is registered as autoload in the namespace of mod or one of its ancestors.
Cool, but in the following snippet ```ruby autoload :Foo, 'foo' autoload?(:Foo) ``` the second line could evaluate to `nil`, and this does not seem to agree. I just registered an autoload, therefore (according to the documentation) I should get "foo" back in line 2. I'd like to ask for clarification from the Ruby team: 1. Is the documentation complete? Should that second line always return "foo"? 2. If the answer is no, which is the logic missing in the docs? Thank you! -- https://bugs.ruby-lang.org/