From: Yusuke Endoh <mame@...>
Date: 2011-12-13T00:14:29+09:00
Subject: [ruby-core:41610] [ruby-trunk - Bug #5750][Open] Thread.current local-variables behavior


Issue #5750 has been updated by Yusuke Endoh.

Status changed from Rejected to Open
Assignee set to Akira Tanaka

Sorry, I was stupid.  Indeed the documatation has room for improvement.
If I recall correctly, akira tanaka suggested the current behavior.
So I'm reopening and assigning this ticket to him.

-- 
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Bug #5750: Thread.current local-variables behavior
http://redmine.ruby-lang.org/issues/5750

Author: Julien A
Status: Open
Priority: Normal
Assignee: Akira Tanaka
Category: 
Target version: 
ruby -v: 1.9.3-p0


Hi, I stumbled upon something which for me is a bug and wanted to check if it is working as intended or not:

    Thread.current[:a] = 1
    p Thread.current[:a] # => 1

    Fiber.new do
     p Thread.current[:a] # => nil
    end.resume


There is clearly a problem in either the documentation or the implementation for me there, we are in the same thread yet the returned values are different which is completely counter intuitive...
Why not add a fiber-variables store to allow the following and keep things separated between fibers and threads

    Fiber.current[:a] = 1
    p Fiber.current[:a] # => 1

    Fiber.new do
     p Fiber.current[:a] # => nil
    end.resume

Which is now the behavior I would expect.




-- 
http://redmine.ruby-lang.org