Split iced_futures into different backend implementations

This commit is contained in:
Héctor Ramón Jiménez 2022-01-28 18:24:07 +07:00
parent 5dab5a327e
commit 167be45a7d
No known key found for this signature in database
GPG key ID: 140CC052C94F138E
19 changed files with 280 additions and 318 deletions

View file

@ -1,12 +1,2 @@
//! Listen and react to time.
pub use crate::runtime::time::{Duration, Instant};
use crate::Subscription;
/// Returns a [`Subscription`] that produces messages at a set interval.
///
/// The first message is produced after a `duration`, and then continues to
/// produce more messages every `duration` after that.
pub fn every(duration: Duration) -> Subscription<Instant> {
iced_futures::time::every(duration)
}
pub use iced_futures::backend::default::time::*;