[ruby-core:24290] Re: [Bug #1717] Thread local variables not visible from within a Fiber

Hi,

2009/7/3 Muhammad Ali <[e-mail]>:
> Thread.current[:x] = 1
>
> Fiber.new{Thread.current[:x]}.resume # => nil
>
> # returns nil when it should return 1
> # even though Thread.current returns the same object


I've heard that this is intentional.  Thread.current is both
thread-local and fiber-local storage.

I can't really remember the rationale, but I think that most of
legacy libraries that uses thread-local storage will expect the
storage to be also fiber-local.

-- 
Yusuke ENDOH <[e-mail]>