Ruby Issue Tracking System

06/06/2018

09:32 PM Ruby Feature #14739: Improve fiber yield/resume performance

I'd like to link this to another open issue regarding Fiber migration between threads. https://bugs.ruby-lang.org/issues/13821
@ioquatix, please note in the above-referenced bug that I put in a link to the "boost" documentation regard... cremes (Chuck Remes)

12/01/2017

09:40 PM Ruby Bug #9664: cannot resume transferred Fiber even if it should resume

This bug or limitation still exists on Ruby 2.4.2. Any plans to address it?
This thread on stackoverflow.com identifies a possible bug in the C code.
https://stackoverflow.com/questions/38199283/ruby-fiber-resuming-transferred-fibe... cremes (Chuck Remes)

04:55 PM Ruby Feature #13893: Add Fiber#[] and Fiber#[]= and restore Thread#[] and Thread#[]= to their original behavior

> One detail, where would we define this Local class?
> ...
The `Local` class is meant to be private. It's behavior should be the same/similar for both Fiber and Thread. Putting it under the Thread namespace makes sense to me since Fibe... cremes (Chuck Remes)

11/30/2017

05:58 PM Ruby Feature #13893: Add Fiber#[] and Fiber#[]= and restore Thread#[] and Thread#[]= to their original behavior

I have an alternative suggestion. Since @shyouhei says that my original suggestion is too difficult a transition path, here is an alternative.
```
# Convenience class to be used by Thread and Fiber. Those classes
# have ... cremes (Chuck Remes)

09/15/2017

04:08 PM Ruby Feature #13821: Allow fibers to be resumed across threads

I took a look at the C++ Boost library boost::fiber documentation. It allows fibers to be detached/attached between threads. Perhaps an explicit API like this is a better approach? See here: http://www.boost.org/doc/libs/1_62_0/libs/fibe... cremes (Chuck Remes)

01:40 PM Ruby Feature #13821: Allow fibers to be resumed across threads

Yes, the Fiber.new(migrate: true) would mean the programmer is taking responsibility for NOT wrapping that Fiber up in mutexes or relying on the default behavior. I think this is reasonable.
As for the async/await code I've written, i... cremes (Chuck Remes)

09/14/2017

05:02 PM Ruby Feature #13893: Add Fiber#[] and Fiber#[]= and restore Thread#[] and Thread#[]= to their original behavior

Ideally some of these changes could be rolled out in 2.x versions with deprecation notices for those methods whose behavior will change or those methods will be eliminated. For the 3.0 release, the deprecated methods should be removed en... cremes (Chuck Remes)

09/12/2017

01:56 PM Ruby Feature #13821: Allow fibers to be resumed across threads

Added ticket 13893 (https://bugs.ruby-lang.org/issues/13893) to track a feature request to cleanup fiber-local and thread-local handling in the Fiber and Thread classes. cremes (Chuck Remes)

01:44 PM Ruby Feature #13821: Allow fibers to be resumed across threads

I understand how this request could allow for race conditions between Fibers. Right now we are relying on the fact that they can only run on a single thread to enforce this particular semantic. I also agree that this is useful in certain... cremes (Chuck Remes)

01:54 PM Ruby Feature #13893 (Open): Add Fiber#[] and Fiber#[]= and restore Thread#[] and Thread#[]= to their original behavior

Ruby 3 API cleanup suggestion.
The Thread and Fiber classes have a very odd API for setting/getting thread local and fiber local variables. With Ruby 3 coming soon, this is a perfect opportunity to make this API more coherent and retu... cremes (Chuck Remes)