From: headius@...
Date: 2015-01-14T22:15:19+00:00
Subject: [ruby-core:67594] [ruby-trunk - Bug #10741] const_defined? triggers autoload where it did not before

Issue #10741 has been updated by Charles Nutter.


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

----------------------------------------
Bug #10741: const_defined? triggers autoload where it did not before
https://bugs.ruby-lang.org/issues/10741#change-51014

* Author: Charles Nutter
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: 2.0.0
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
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.



-- 
https://bugs.ruby-lang.org/