tenderlove / ruby-lang.org wrote:
> Thanks for the patch.  That indeed fixes it for me.  Can you apply it?

Thanks for the confirmation, r53518

> I guess this is due to the hash table change?  I can't say I fully understand
> why this fixes it, besides pre-populating the cache.

Yes, it used to be order-dependent.

Populating the cache early means we resolve the name before other entries
have a chance to mess with the ordering.  So when an entry is inserted
relative to another still affects how its name is resolved.

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>