Apologies in advance if this is the wrong place to get clarification: It's been widely circulated that autoload is deprecated - http://www.ruby-forum.com/topic/3036681 - does this patch change that stance? I ask because autoload still ...Nevir (Ian MacLeod)
Let me see if I understand the implicit conversion cases: * If an object implements #to_ary, #to_str, etc - it is asserting that it is close enough to the desired type in behavior that we don't need to perform an explicit coercion? * I....Nevir (Ian MacLeod)
This seems similar to http://bugs.ruby-lang.org/issues/6923 Example: irb(main):001:0> class Thing irb(main):002:1> include Enumerable irb(main):003:1> def each(*args, &block) irb(main):004:2> [1,2,3,4,5]....Nevir (Ian MacLeod)
Why would you need to call fetch with a block if you already know the index is out of range? You already have the index you're calling with...Nevir (Ian MacLeod)
This also occurs on Ruby 1.8. First, the example, taken almost directly from the docs (except the docs only describe the fetch(4) case): irb(main):001:0> a = [11, 22, 33, 44] => [11, 22, 33, 44] irb(main):002:0> a.fetch(0) { |i| ...Nevir (Ian MacLeod)
One additional note is that this only seems to occur when `\W` is in a character group: ~~~ ➜ ruby -ve '("a".."z").each {|ch| p(/\W/i.match(ch)) }' ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin12.0.0] nil nil nil n...Nevir (Ian MacLeod)
Nevir (Ian MacLeod)11:22 AM Ruby Bug #921: autoload is not thread-safe