[#88925] [Ruby trunk Feature#15095] [PATCH] share VM stack between threads and fibers if identical — ko1@...
Issue #15095 has been updated by ko1 (Koichi Sasada).
4 messages
2018/09/09
[#88927] Re: [Ruby trunk Feature#15095] [PATCH] share VM stack between threads and fibers if identical
— Eric Wong <normalperson@...>
2018/09/09
[email protected] wrote:
[#88926] [Ruby trunk Feature#15095] [PATCH] share VM stack between threads and fibers if identical — ko1@...
Issue #15095 has been updated by ko1 (Koichi Sasada).
3 messages
2018/09/09
[#89218] [Ruby trunk Bug#15130] open-uri hangs on cygwin — duerst@...
SXNzdWUgIzE1MTMwIGhhcyBiZWVuIHVwZGF0ZWQgYnkgZHVlcnN0IChNYXJ0aW4gRMO8cnN0KS4K
5 messages
2018/09/30
[ruby-core:88992] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
From:
Eric Wong <normalperson@...>
Date:
2018-09-13 09:18:36 UTC
List:
ruby-core #88992
[email protected] wrote: > The latest proposal includes time slice scheduling, so it is > not a cooperative thread. Thanks for the comment. I haven't implemented timeslice, yet, so I won't :) > I object to the name `Thread::Coro`. If being lightweight is > the biggest characteristic, it should be `Thread::Lite` or > `Thread::Light`. Thread::Light is probably acceptable, I still prefer "Coro" in name. Is "Thread.light {}" shortcut for "Thread::Light.new {}" acceptable? I am strongly against "Lite", it sounds like an advertisement for foods which may cause cancer. Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
