From: "nobu (Nobuyoshi Nakada)" <nobu@...>
Date: 2013-04-16T17:03:41+09:00
Subject: [ruby-core:54329] [ruby-trunk - Feature #8215] Support accessing Fiber-locals and backtraces for a Fiber


Issue #8215 has been updated by nobu (Nobuyoshi Nakada).

File 0001-cont.c-fiber-local-accessors.patch added

More tests may be needed.
----------------------------------------
Feature #8215: Support accessing Fiber-locals and backtraces for a Fiber
https://bugs.ruby-lang.org/issues/8215#change-38609

Author: halorgium (Tim Carey-Smith)
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 


=begin
As part of debugging celluloid, I have been wanting to diagnose where the Fibers are running and their various locals.

I would expect the following to work.

  Thread.current[:key] = "outside"
  fiber = Fiber.new do
    Thread.current[:key] = "inside"
    Fiber.yield
  end
  fiber.resume
  fiber[:key] == "inside" # true
  fiber.backtrace # ...

I also wonder whether (({Fiber#[]})) should be implemented, so (({Fiber.current[:key]})) is possible.

For reference, here is the issue on the rubinius issue tracker: ((<"github/rubinius/rubinius/2200"|URL:https://github.com/rubinius/rubinius/issues/2200>))
=end



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