mirror of
https://github.com/tokio-rs/tokio.git
synced 2026-08-15 00:00:15 +02:00
Carl Lerche
cf184eb326
* Remove `counted` field on `timer::Entry`. It turns out that a better indicator of whether or not the number of active timeouts should be decremented is if the `Entry` has been associated with a timer. In other words, if `Entry::inner` can be upgraded, then the count should be decremented on drop. * timer: Tweak link between `Delay` and the driver This tweaks the struct layout / details regarding how a `Delay` instance is linked to a driver (timer instance). Instead of lazily allocating the `Entry` (node shared between `Delay` and the timer), `Entry` is allocated immediately when `Delay` is created. This allows using the entry store data used by `Delay`. This is in anticipation of further timer improvements that would otherwise require the size of `Delay` to grow further. Since an allocation is already made, the idea is to shrink the size of the `Delay` struct.
30 lines
702 B
TOML
30 lines
702 B
TOML
[package]
|
|
name = "tokio-timer"
|
|
# When releasing to crates.io:
|
|
# - Update html_root_url.
|
|
# - Update CHANGELOG.md.
|
|
# - Create "v0.2.x" git tag.
|
|
version = "0.2.5"
|
|
authors = ["Carl Lerche <[email protected]>"]
|
|
license = "MIT"
|
|
readme = "README.md"
|
|
repository = "https://github.com/tokio-rs/tokio"
|
|
homepage = "https://github.com/tokio-rs/tokio"
|
|
documentation = "https://docs.rs/tokio-timer"
|
|
description = """
|
|
Timer facilities for Tokio
|
|
"""
|
|
|
|
[dependencies]
|
|
futures = "0.1.19"
|
|
tokio-executor = { version = "0.1.1", path = "../tokio-executor" }
|
|
crossbeam-utils = "0.5.0"
|
|
|
|
# Backs `DelayQueue`
|
|
slab = "0.4.1"
|
|
|
|
[dev-dependencies]
|
|
rand = "0.5"
|
|
tokio-mock-task = "0.1.0"
|
|
tokio = { version = "0.1.7", path = "../" }
|