5 releases

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

Download history 13331/week @ 2018-05-16 16125/week @ 2018-05-23 15498/week @ 2018-05-30 17236/week @ 2018-06-06 15848/week @ 2018-06-13 17332/week @ 2018-06-20 16300/week @ 2018-06-27 14484/week @ 2018-07-04 17324/week @ 2018-07-11 17180/week @ 2018-07-18 16248/week @ 2018-07-25 15983/week @ 2018-08-01 19484/week @ 2018-08-08

70,790 downloads per month

tokio-executor

Task execution related traits and utilities.

Documentation

Overview

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:

  • The Executor trait describes the API for spawning a future onto an executor.

  • enter marks 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.

  • DefaultExecutor spawns tasks onto the default executor for the current context.

  • Park abstracts over blocking and unblocking the current thread.

License

This project is licensed under the MIT license.

Contribution

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.

MIT license

Dependencies

Reverse deps