Issue #21154 has been updated by fxn (Xavier Noria). mame (Yusuke Endoh) wrote in #note-29:
As for autoload with a full path, it would be easy (and that's the case for Zeitwerk, I think).
Correct, Zeitwerk only sets autoloads with absolute paths (that may contain symlinks).
In general, autoload with a relative path needs to resolve the path to absolute one. This resolution may be too costly to do for all autoload calls by default.
And that is what the predicate `autoload?` is doing, which is the origin of this ticket. I don't even know if that is intentional of it is implementation leaking (I'd expect `autoload?` to simply return the configured path or `nil` right away, and have the circularity check when the autoload is hit.) ---------------------------------------- Misc #21154: Document or change Module#autoload? https://bugs.ruby-lang.org/issues/21154#change-112724 * 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/