ko1 brought up a good point:  this may interact badly with
3rd-party libraries which use thread-local storage via
pthread_getspecific/pthread_setspecific (or compiler
extensions).

On one hand, I expected this to be beneficial for malloc
implementations which use thread-specific storage (most all of
them do); but there may be problems in 3rd-party libraries we do
not know about...

So, we might need to disable this before 2.6 release :<

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