General

Profile

cremes (Chuck Remes)

  • Registered on: 01/10/2016
  • Last connection: 09/29/2017

Issues

Activity

09/15/2017

04:08 PM Ruby trunk 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 t...
01:40 PM Ruby trunk 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 i...

09/14/2017

05:02 PM Ruby trunk 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 be...

09/12/2017

01:56 PM Ruby trunk 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 th...
01:54 PM Ruby trunk 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 a...
01:44 PM Ruby trunk 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 th...

08/16/2017

05:19 PM Ruby trunk Feature #13821 (Assigned): Allow fibers to be resumed across threads
Given a Fiber created in ThreadA, Ruby 2.4.1 (and earlier releases) raise a FiberError if the fiber is resumed in Thr...

01/26/2016

09:05 PM Ruby trunk Misc #12004: Code of Conduct
#433 Kurtis Rainbolt-Greene wrote:
*Done. See: Backlog.*
No. NOT done. I've read this entire thread and I haven't...
04:58 PM Ruby trunk Misc #12004: Code of Conduct
In #371, Kurtis Rainbolt-Greene listed several projects that have adopted the CoC and asked if any of the feared down...

01/21/2016

01:26 PM Ruby trunk Misc #12004: Code of Conduct
I am not in favor of the adoption of a CoC.
If this solved a real problem, I would consider it as would any reason...

Also available in: Atom