Jose Valim implies that autoloading is threadsafe in Ruby 2.0: The issue with this approach is that it is not thread-safe, except for> latest JRuby versions (since 1.7) and Ruby master (2.0)http://blog.plataformatec.com.br/2012/08/eager-loading-for-greater-good>However, the autoload bug ticket filed against Ruby (http://bugs.ruby-lang.org/issues/921) was closed and refers to a forum post wherein Matz recommends *not* to use autload (http://www.ruby-forum.com/topic/3036681). Does anyone have any light to shed on this discrepancy? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/0a11bc68-756f-4de2-a4bb-afb23a92d2f6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Here''s a link that''s a little more current that sheds some light on the issue: https://github.com/rkh/rack-protection/issues/45 On Saturday, June 15, 2013 9:10:10 PM UTC-4, Josh Jordan wrote:> > Jose Valim implies that autoloading is threadsafe in Ruby 2.0: > > The issue with this approach is that it is not thread-safe, except for >> latest JRuby versions (since 1.7) and Ruby master (2.0) > > > > http://blog.plataformatec.com.br/2012/08/eager-loading-for-greater-good >> > > However, the autoload bug ticket filed against Ruby ( > http://bugs.ruby-lang.org/issues/921) was closed and refers to a forum > post wherein Matz recommends *not* to use autload ( > http://www.ruby-forum.com/topic/3036681). > > Does anyone have any light to shed on this discrepancy? >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/10b01939-6267-4347-b32b-7b52c31e4f85%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
josh.jordan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2013-Jun-16 15:29 UTC
Re: Re: Autload thread safety in Ruby 2.0?
Thanks, Rick. I''ve asked the question on that thread as well. It seems to suffer from the same issue: its just a claim that appears to conflict with Matz''s implication from the same post I included in my original question. On Sun, Jun 16, 2013 at 9:14 AM, Rick <richard.t.lloyd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Here''s a link that''s a little more current that sheds some light on the > issue: https://github.com/rkh/rack-protection/issues/45 > > > On Saturday, June 15, 2013 9:10:10 PM UTC-4, Josh Jordan wrote: >> >> Jose Valim implies that autoloading is threadsafe in Ruby 2.0: >> >> The issue with this approach is that it is not thread-safe, except for >>> latest JRuby versions (since 1.7) and Ruby master (2.0) >> >> >> >> http://blog.plataformatec.com.**br/2012/08/eager-loading-for-** >>> greater-good<http://blog.plataformatec.com.br/2012/08/eager-loading-for-greater-good> >>> >> >> However, the autoload bug ticket filed against Ruby ( >> http://bugs.ruby-lang.org/**issues/921<http://bugs.ruby-lang.org/issues/921>) >> was closed and refers to a forum post wherein Matz recommends *not* to >> use autload (http://www.ruby-forum.com/**topic/3036681<http://www.ruby-forum.com/topic/3036681> >> ). >> >> Does anyone have any light to shed on this discrepancy? >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ruby on Rails: Talk" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/rubyonrails-talk/cD3Ha2m-esA/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/10b01939-6267-4347-b32b-7b52c31e4f85%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CA%2BSXTRjxtyYwmmsNkQcr2Hxro%2BkUqECZD8UFRouyh3hm60r_SA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.