From: Jim Deville <jdeville@...>
Date: 2008-12-03T14:55:25+09:00
Subject: [ruby-core:20248] Re: autoload and concurrency

I was keying off of this:

The worst part is that no user action can solve this problem: because autoloading is magic, it's impossible for the user to lock the resulting require. In effect, this makes autoloading completely useless for threaded environments. Is this intentional?

However, I think the idea of a require plugin makes more sense. I'm assuming something like a callback like extend and include do, although I'm not sure if that could provide a lock without a shared data structure.

JD

-----Original Message-----
From: Charles.O.Nutter@sun.com [mailto:Charles.O.Nutter@sun.com] On Behalf Of Charles Oliver Nutter
Sent: Tuesday, December 02, 2008 8:53 PM
To: ruby-core@ruby-lang.org
Subject: [ruby-core:20240] Re: autoload and concurrency

Jim Deville wrote:
> This seems like a strong argument in favor of Ruby-core:20225.

Fixing autoload to call require doesn't solve anything because there's
still the exact same gap between the time it deletes the special value
and the time when the required file redefines it.

- Charlie