Carl Lerche 65cbfced29
Poll evented mutability (#37)
Generally speaking, it is unsafe to access to perform asynchronous
operations using `&self`. Taking `&self` allows usage from a `Sync`
context, which has unexpected results.

Taking `&mut self` to perform these operations prevents using these
asynchronous values from across tasks (unless they are wrapped in
`RefCell` or `Mutex`.
2018-01-31 20:09:15 -08:00
2017-12-05 09:02:07 -08:00
2018-01-31 20:09:15 -08:00
2018-01-31 20:09:15 -08:00
2018-01-31 20:09:15 -08:00
2018-01-30 13:27:12 -08:00
2018-01-30 13:27:12 -08:00
2016-08-26 14:56:21 -07:00
2016-08-26 14:56:21 -07:00

tokio

A work-in-progress rearchitecting of the tokio-core crate in line with tokio-rs/tokio-rfcs#3

Build Status Build status

Documentation

Usage

This project is a work in progress, more information will be added here as it progresses.

License

This project is licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tokio by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Description
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Readme MIT 75 MiB
Languages
Rust 100%