Consists of the id and result of the select operation that was completed
A golang style channel implementation with buffered and unbuffered operation modes
A Fiber level Mutex, essentially a binary FiberSemaphore
An example Scheduler using Fibers.
A Fiber level Semaphore
Block on multiple Channels
Get current running FiberScheduler
Set current running FiberScheduler
A common interface for objects that can be used in select()
An aggregate to hold neccessary information for a select operation
A simple spinlock
<a href="http://www.boost.org/LICENSE_1_0.txt">Boost License 1.0</a>.
Copyright Sean Kelly 2009 - 2014.
This is a low-level messaging API upon which more structured or restrictive APIs may be built. The general idea is that every messageable entity is represented by a common handle type called a Tid, which allows messages to be sent to logical threads that are executing in both the current process and in external processes using the same interface. This is an important aspect of scalability because it allows the components of a program to be spread across available resources with few to no changes to the actual implementation.
A logical thread is an execution context that has its own stack and which runs asynchronously to other logical threads. These may be preemptively scheduled kernel threads, fibers (cooperative user-space threads), or some other concept with similar behavior.
The type of concurrency used when logical threads are created is determined by the Scheduler selected at initialization time. The default behavior is currently to create a new kernel thread per call to spawn, but other schedulers are available that multiplex fibers across the main thread or use some combination of the two approaches.
Note: Copied (almost verbatim) from Phobos at commit 3bfccf4f1 (2019-11-27) Changes are this notice, and the module rename, from std.concurrency to geod24.concurrency.