commit | 33bdc2fc06789fcbd94d2c49dc473cf879794448 | [log] [tgz] |
---|---|---|
author | Carl Lerche <me@carllerche.com> | Fri Mar 23 11:03:29 2018 -0700 |
committer | Carl Lerche <me@carllerche.com> | Fri Mar 23 11:42:46 2018 -0700 |
tree | d1327905d17b2d6528adae4567924c76317820e4 | |
parent | 9a39f31933a7d8c299f5746f41854fd53a2b9df0 [diff] |
Fix bug where the wrong readiness is cleared This is a backport of the fix provided by tokio-rs/tokio#250 Closes #317
This crate is scheduled for deprecation in favor of tokio.
tokio-core
is still actively maintained, but only bug fixes will be applied. All new feature development is happening in tokio.
Core I/O and event loop abstraction for asynchronous I/O in Rust built on futures
and mio
.
First, add this to your Cargo.toml
:
[dependencies] tokio-core = "0.1"
Next, add this to your crate:
extern crate tokio_core;
You can find extensive documentation and examples about how to use this crate online at https://tokio.rs as well as the examples
folder in this repository. The API documentation is also a great place to get started for the nitty-gritty.
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tokio-core by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.