|
| From: | Dmitry Gutov |
| Subject: | Re: Concurrency, again |
| Date: | Wed, 26 Oct 2016 01:28:49 +0300 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Thunderbird/50.0 |
On 25.10.2016 16:34, Philipp Stephani wrote:
I'd suggest to adapt the terminology accordingly: "thread" *can* of course mean "cooperative userland thread", but for most programmers it has come to mean "OS-level parallel thread with preemptive kernel-level scheduling". Should we avoid this term and use "coroutine" instead?
Or "fiber" [0], which might be more familiar to at least some Ruby, D and .NET programmers [1].
[0] https://en.wikipedia.org/wiki/Fiber_(computer_science)[1] https://en.wikipedia.org/wiki/Coroutine#Implementation_in_the_.NET_Framework_as_fibers
| [Prev in Thread] | Current Thread | [Next in Thread] |