From: jonathan rochkind <jonathan@...>
Date: 2011-11-22T09:57:54+09:00
Subject: [ruby-core:41183] [ruby-trunk - Feature #5653] "I strongly discourage the use of autoload in any standard libraries" (Re: autoload will be dead)


Issue #5653 has been updated by jonathan rochkind.


My understanding was that plain old 'require' had much the same flaw in a multi-threaded environment as autoload. No?
----------------------------------------
Feature #5653: "I strongly discourage the use of autoload in any standard libraries" (Re: autoload will be dead)
http://redmine.ruby-lang.org/issues/5653

Author: Yukihiro Matsumoto
Status: Open
Priority: Normal
Assignee: 
Category: lib
Target version: 2.0.0


 Hi,
 
 Today, I talked with NaHi about enhancing const_missing to enable
 autoload-like feature with nested modules.  But autoload itself has
 fundamental flaw under multi-thread environment.  I should have remove
 autoload when I added threads to the language (threads came a few
 months after autoload).
 
 So I hereby declare the future deprecation of autoload.  Ruby will
 keep autoload for a while, since 2.0 should keep compatibility to 1.9.
 But you don't expect it will survive further future, e.g. 3.0.
 
 I strongly discourage the use of autoload in any standard libraries.
 
 							matz.


-- 
http://redmine.ruby-lang.org