[#84867] [Ruby trunk Bug#14357] thread_safe tests suite segfaults — v.ondruch@...
Issue #14357 has been reported by vo.x (Vit Ondruch).
11 messages
2018/01/15
[#85364] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/03
[email protected] wrote:
[#85368] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/03
Eric Wong wrote:
[#85442] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/06
Eric Wong <[email protected]> wrote:
[#85451] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Vladimir Makarov <vmakarov@...>
2018/02/06
On 02/06/2018 05:00 AM, Eric Wong wrote:
[#85455] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults
— Eric Wong <normalperson@...>
2018/02/06
Vladimir Makarov <[email protected]> wrote:
[#84874] [Ruby trunk Bug#14360] Regression CSV#open method for writing from Ruby 2.4.3 to 2.5.0 — shevegen@...
Issue #14360 has been updated by shevegen (Robert A. Heiler).
3 messages
2018/01/15
[#84980] [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — hsbt@...
Issue #13618 has been updated by hsbt (Hiroshi SHIBATA).
10 messages
2018/01/23
[#85012] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/01/23
[email protected] wrote:
[#85081] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/01/24
Eric Wong <[email protected]> wrote:
[#85082] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/01/24
> Thinking about this even more; I don't think it's possible to
[#85088] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — danieldasilvaferreira@...
Issue #13618 has been updated by dsferreira (Daniel Ferreira).
3 messages
2018/01/25
[#85107] [Ruby trunk Misc#14222] Mutex.lock is not safe inside signal handler: what is? — eregontp@...
Issue #14222 has been updated by Eregon (Benoit Daloze).
3 messages
2018/01/25
[#85136] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — Eric Wong <normalperson@...>
[email protected] wrote:
3 messages
2018/01/26
[ruby-core:85193] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
From:
Eric Wong <normalperson@...>
Date:
2018-01-28 21:19:44 UTC
List:
ruby-core #85193
[email protected] wrote: > normalperson (Eric Wong) wrote: > > > No, I'm against making major changes. For 2, I mean we limit > usage to queues for now, which is a a subset of 1; but I'm also > OK implementing mutex/condvar support for 1. > > > Having less things to learn is better for adoption and improving > usefulness > > I would agree with that comment if the "less" doesn't imply in itself an overlap of confusions. > How will be the documentation? We need to think very careful about that. I prefer minimal documentation and having it do obvious/predictable things which are already familiar to existing users of Thread. In my experience, too much documentation overhwhelms users and they ignore it. And about the comments you see from developers here: the vast majority of Ruby users will never read or see them even. There's too much to read for most people. > > Too obscure and not obvious for me; do non-Lua people know about it? > > Do we have Threadlets in other languages? > It seems Lua has got something very similar (how similar?) and calls it Lanes. > Am I wrong with this assumption? The "let" suffix is commonly associated with a smaller version of something; and the "Thread" prefix already exists; so it should be immediately familiar (at least to English speakers) > > When comparing to physical objects, it seems more appropriate for > something like a channel or pipe. > > In a dedicated Lane I see "vehicles" moving steady and fast in between the traffic chaos. > I consider it a fortunate choice from Lua people. > The notion of async for me is management of traffic in between the chaos. > Why thread? Because it is a kind of channel or pipe as well, isn't it? Not exactly. Pipes are a type of queue (ring buffer), it is something which data passes through. Threads/Processes/Fibers are execution contexts which can use pipes/queues to pass data along. Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
