#timer #async

no-std async-timer

Timers for Rust async story

40 releases ()

1.0.0-beta.13 Mar 23, 2024
1.0.0-beta.11 Oct 27, 2023
1.0.0-beta.9 Mar 12, 2023
1.0.0-beta.8 Dec 31, 2021
0.2.10 Jul 15, 2019

#25 in WebAssembly

Download history 2858/week @ 2023-12-23 5992/week @ 2023-12-30 3208/week @ 2024-01-06 5448/week @ 2024-01-13 2332/week @ 2024-01-20 2711/week @ 2024-01-27 3019/week @ 2024-02-03 3596/week @ 2024-02-10 3696/week @ 2024-02-17 5111/week @ 2024-02-24 4646/week @ 2024-03-02 8950/week @ 2024-03-09 7496/week @ 2024-03-16 6934/week @ 2024-03-23 6829/week @ 2024-03-30 5198/week @ 2024-04-06

27,587 downloads per month
Used in 30 crates (16 directly)

BSL-1.0 license

64KB
1.5K SLoC

async-timer

Rust Crates.io Documentation dependency status

Timer facilities for Rust's async story

Accuracy

Regular timers that do not rely on async event loop tend to be on par with user space timers like in tokio. If that's not suitable for you you should enable event loop based timers which in most cases give you the most accurate timers possible on unix platforms (See features.)

Features

  • tokio1 - Enables event loop based timers using tokio, providing higher resolution timers on unix platforms.
  • c_wrapper - Uses C shim to create bindings to platform API, which may be more reliable than libc.
  • std - Enables usage of std types (e.g. Error)

Examples

Timed

async fn job() {
}

async fn do_job() {
    let work = unsafe {
        async_timer::Timed::platform_new_unchecked(job(), core::time::Duration::from_secs(1))
    };

    match work.await {
        Ok(_) => println!("I'm done!"),
        //You can retry by polling `expired`
        Err(expired) => println!("Job expired: {}", expired),
    }
}

Interval

async fn job() {
}

async fn do_a_while() {
    let mut times: u8 = 0;
    let mut interval = async_timer::Interval::platform_new(core::time::Duration::from_secs(1));

    while times < 5 {
        job().await;
        interval.wait().await;
        times += 1;
    }
}

Dependencies

~0–11MB
~75K SLoC