[ruby-core:54457] [ruby-trunk - Feature #8215] Support accessing Fiber-locals and backtraces for a Fiber

["halorgium (Tim Carey-Smith)" <ruby-lang@spam.halorgium.net>]

Issue #8215 has been updated by halorgium (Tim Carey-Smith).


I realised that this might be better in common-ruby. 
I originally proposed the idea with RBX. 
Could someone move it?
----------------------------------------
Feature #8215: Support accessing Fiber-locals and backtraces for a Fiber
https://bugs.ruby-lang.org/issues/8215#change-38739

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/