Expand description
§Async time operators.
This crate provides ergonomic, async time-based operations. It serves as an
experimental playground to experiment with how we could potentially add
time-based operations to async-std, and subsequently the stdlib.
The goal is to make working with time and other events feel natural. A major source of inspiration for this has been RxJS, which uses events (including time) to trigger operations. This crate takes that principle, inverts the model to make it evaluate lazily, and wraps it in an ergnomic Rust interface.
§Examples
Delay a future’s execution by 100ms
use futures_time::prelude::*;
use futures_time::time::Duration;
async_io::block_on(async {
let res = async { "meow" }
.delay(Duration::from_millis(100))
.await;
assert_eq!(res, "meow");
})Error if a future takes longer than 200ms
use futures_time::prelude::*;
use futures_time::time::Duration;
async_io::block_on(async {
let res = async { "meow" }
.delay(Duration::from_millis(100))
.timeout(Duration::from_millis(200))
.await;
assert_eq!(res.unwrap(), "meow");
})Throttle a stream
This lets two items through in total: one 100ms after the program has
started, and one 300ms after the program has started.
use futures_lite::prelude::*;
use futures_time::prelude::*;
use futures_time::time::Duration;
use futures_time::stream;
async_io::block_on(async {
let mut counter = 0;
stream::interval(Duration::from_millis(100)) // Yield an item every 100ms
.take(4) // Stop after 4 items
.throttle(Duration::from_millis(300)) // Only let an item through every 300ms
.for_each(|_| counter += 1) // Increment a counter for each item
.await;
assert_eq!(counter, 2);
})§The Timer trait
The future returned by task::sleep implements the future::Timer
trait. This represents a future whose deadline can be moved forward into the
future.
For example, say we have a deadline of Duration::from_secs(10). By calling
Timer::reset_timer the timer can be reschedule to trigger at a later time.
This functionality is required for methods such as debounce and
Stream::timeout, which will regularly want to reschedule their timers to trigger
the future.
Currently the only type implementing the Timer trait is
task::Sleep, which is created from a Duration. This is in contrast
with task::sleep_until, which takes an Instant, and cannot be reset.
§Cancellation
You can use channel::bounded to create a channel::Sender and channel::Receiver pair.
When the “sender” sends a message, all “receivers” will halt execution of the future the next time they are
.awaited. This will cause the future to stop executing, and all
destructors to be run.
use futures_lite::prelude::*;
use futures_time::prelude::*;
use futures_time::channel;
use futures_time::time::Duration;
async_io::block_on(async {
let (send, mut recv) = channel::bounded::<()>(1); // create a new send/receive pair
let mut counter = 0;
let value = async { "meow" }
.delay(Duration::from_millis(100))
.timeout(recv.next()) // time-out when the sender emits a message
.await;
assert_eq!(value.unwrap(), "meow");
})§Futures
Future::delayDelay execution for a specified time.Future::timeoutCancel the future if the execution takes longer than the specified time.Future::parkSuspend or resume the execution of a future.
§Tasks
task::sleep_untilSleeps until the specified deadline.task::sleepSleeps for the specified amount of time.
§Streams
Stream::bufferReturns a stream which buffers items and flushes them at each interval.Stream::debounceReturns a stream that debounces for the given duration.Stream::delayDelay execution for a specified time.Stream::parkSuspend or resume the execution of a stream.Stream::sampleYield the last value received, if any, at each interval.Stream::throttleFilter out all items after the first for a specified time.Stream::timeoutCancel the stream if the execution takes longer than the specified time.stream::intervalCreates a new stream that yields at a set interval.
§Re-exports
channelis a re-export of theasync-channelcrate, exposed for convenience