Travis Bischel b9dc4c9008 TokenTimeout: add doc around new panic
My slab bump in #246 added a potential new panic in Core's Inner's
`cancel_timeout`.

Thankfully, the only way `cancel_timeout` can be called is from
TimeoutToken's `cancel_timeout`, which is crate-internal only and is
only called from Timeout's and Interval's drop fn's.

This change simply adds new clarifying documentation around
TokenTimeout's cancel_timeout to "future proof" anybody looking to use
cancel_timeout directly (not just on drop).
2017-09-08 22:31:37 -07:00
2017-05-30 11:23:34 -07:00
2017-08-24 08:16:04 -07:00
2017-05-08 16:18:42 -07:00
2016-11-19 09:40:33 -08:00
2016-08-26 14:45:55 -07:00
2017-09-07 20:53:54 -07:00
2016-08-26 14:56:21 -07:00
2016-08-26 14:56:21 -07:00
2017-01-11 09:14:50 -08:00

tokio-core

Core I/O and event loop abstraction for asynchronous I/O in Rust built on futures and mio.

Build Status Build status

Documentation

Tutorial

Usage

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.

License

tokio-core is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.

See LICENSE-APACHE, and LICENSE-MIT for details.

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