|0.1.3||Aug 7, 2018|
|0.1.2||Mar 30, 2018|
|0.1.1||Mar 23, 2018|
|0.1.0||Mar 9, 2018|
|0.0.0||Feb 1, 2018|
#7 in Concurrency
70,790 downloads per month
Task execution related traits and utilities.
In the Tokio execution model, futures are lazy. When a future is created, no work is performed. In order for the work defined by the future to happen, the future must be submitted to an executor. A future that is submitted to an executor is called a "task".
The executor is responsible for ensuring that [
Future::poll] is called
whenever the task is [notified]. Notification happens when the internal state of
a task transitions from "not ready" to ready. For example, a socket might have
received data and a call to
read will now be able to succeed.
This crate provides traits and utilities that are necessary for building an executor, including:
Executortrait describes the API for spawning a future onto an executor.
entermarks that the the current thread is entering an execution context. This prevents a second executor from accidentally starting from within the context of one that is already running.
DefaultExecutorspawns tasks onto the default executor for the current context.
Parkabstracts over blocking and unblocking the current thread.
This project is licensed under the MIT license.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tokio by you, shall be licensed as MIT, without any additional terms or conditions.
- futures 0.1.19