Project

General

Profile

Bug #10741

const_defined? triggers autoload where it did not before

Added by headius (Charles Nutter) over 4 years ago. Updated over 4 years ago.

Status:
Open
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:67591]

Description

This should not cause b.rb to load, but it does in 2.2:

~/projects/jruby $ cat a.rb
module Foo
autoload :Bar, 'b.rb'
end

p Foo.const_defined?('Bar')

~/projects/jruby $ cat b.rb
puts "in b"
module Foo
Bar = 1
end

~/projects/jruby $ rvm ruby-2.0 do ruby -I. a.rb
true

~/projects/jruby $ rvm ruby-2.1 do ruby -I. a.rb
in b
true

~/projects/jruby $ rvm ruby-2.2 do ruby -I. a.rb
in b
true

This is likely caused by the :: support in const_get/const_defined not doing autoload-free traversal.

History

Updated by headius (Charles Nutter) over 4 years ago

To be more specific, this assertion fails on MRI:

assert_equal("#{File.dirname(FILE)}/autoloaded.rb", Object.autoload?("Autoloaded"))

Because the previous const_defined? call has already triggered the autoload.

Updated by headius (Charles Nutter) over 4 years ago

Boo...my fix was bad because it stopped searching superclasses. Since I did not have an appropriate method to search superclasses, split up :: elements, and check private consts all in one, I reverted JRuby to the autoload-inducing state for now: https://github.com/jruby/jruby/commit/ccfee85c717a8235d18c63aacfe5f015f4f14261

Tagged some specs and removed an assertion in JRuby's test: https://github.com/jruby/jruby/commit/cffeaab92d5a893240f6ba35159c29eb4cc8d4d5

Also available in: Atom PDF