Files
tokio/tokio-timer/src/delay.rs
T

109 lines
3.1 KiB
Rust
Raw Normal View History

2018-03-28 22:26:47 -07:00
use Error;
use timer::Registration;
use futures::{Future, Poll};
use std::time::Instant;
/// A future that completes at a specified instant in time.
///
2018-03-30 14:21:48 -07:00
/// Instances of `Delay` perform no work and complete with `()` once the
2018-03-28 22:26:47 -07:00
/// specified deadline has been reached.
///
2018-03-30 14:21:48 -07:00
/// `Delay` has a resolution of one millisecond and should not be used for tasks
2018-03-28 22:26:47 -07:00
/// that require high-resolution timers.
///
/// [`new`]: #method.new
#[derive(Debug)]
2018-03-30 14:21:48 -07:00
pub struct Delay {
2018-03-28 22:26:47 -07:00
/// The instant at which the future completes.
deadline: Instant,
2018-03-30 14:21:48 -07:00
/// The link between the `Delay` instance at the timer that drives it.
2018-03-28 22:26:47 -07:00
///
2018-03-30 14:21:48 -07:00
/// When `Delay` is created with `new`, this is initialized to `None` and is
2018-03-28 22:26:47 -07:00
/// lazily set in `poll`. When `poll` is called, the default for the current
/// execution context is used (obtained via `Handle::current`).
///
2018-03-30 14:21:48 -07:00
/// When `delay` is created with `new_with_registration`, the value is set.
2018-03-28 22:26:47 -07:00
///
/// Once `registration` is set to `Some`, it is never changed.
registration: Option<Registration>,
}
2018-03-30 14:21:48 -07:00
impl Delay {
/// Create a new `Delay` instance that elapses at `deadline`.
2018-03-28 22:26:47 -07:00
///
/// Only millisecond level resolution is guaranteed. There is no guarantee
/// as to how the sub-millisecond portion of `deadline` will be handled.
2018-03-30 14:21:48 -07:00
/// `Delay` should not be used for high-resolution timer use cases.
pub fn new(deadline: Instant) -> Delay {
Delay {
2018-03-28 22:26:47 -07:00
deadline,
registration: None,
}
}
pub(crate) fn new_with_registration(
deadline: Instant,
2018-03-30 14:21:48 -07:00
registration: Registration) -> Delay
2018-03-28 22:26:47 -07:00
{
2018-03-30 14:21:48 -07:00
Delay {
2018-03-28 22:26:47 -07:00
deadline,
registration: Some(registration),
}
}
/// Returns the instant at which the future will complete.
pub fn deadline(&self) -> Instant {
self.deadline
}
2018-03-30 14:21:48 -07:00
/// Returns true if the `Delay` has elapsed
2018-03-28 22:26:47 -07:00
///
2018-03-30 14:21:48 -07:00
/// A `Delay` is elapsed when the requested duration has elapsed.
2018-03-28 22:26:47 -07:00
pub fn is_elapsed(&self) -> bool {
self.registration.as_ref()
.map(|r| r.is_elapsed())
.unwrap_or(false)
}
2018-03-30 14:21:48 -07:00
/// Reset the `Delay` instance to a new deadline.
2018-03-28 22:26:47 -07:00
///
2018-03-30 14:21:48 -07:00
/// Calling this function allows changing the instant at which the `Delay`
2018-03-28 22:26:47 -07:00
/// future completes without having to create new associated state.
///
/// This function can be called both before and after the future has
/// completed.
pub fn reset(&mut self, deadline: Instant) {
self.deadline = deadline;
if let Some(registration) = self.registration.as_ref() {
registration.reset(deadline);
}
}
2018-03-30 14:21:48 -07:00
/// Register the delay with the timer instance for the current execution
2018-03-28 22:26:47 -07:00
/// context.
fn register(&mut self) {
if self.registration.is_some() {
return;
}
self.registration = Some(Registration::new(self.deadline));
}
}
2018-03-30 14:21:48 -07:00
impl Future for Delay {
2018-03-28 22:26:47 -07:00
type Item = ();
type Error = Error;
fn poll(&mut self) -> Poll<Self::Item, Self::Error> {
2018-03-30 14:21:48 -07:00
// Ensure the `Delay` instance is associated with a timer.
2018-03-28 22:26:47 -07:00
self.register();
self.registration.as_ref().unwrap()
.poll_elapsed()
}
}