Files
tokio/tokio-signal/examples/ctrl-c.rs
T

46 lines
1.6 KiB
Rust
Raw Normal View History

2019-05-14 10:27:36 -07:00
#![deny(warnings, rust_2018_idioms)]
2019-07-03 10:40:59 -07:00
#![feature(async_await)]
2019-05-14 10:27:36 -07:00
2019-07-03 10:40:59 -07:00
use futures_util::stream::StreamExt;
2016-09-08 17:13:18 -07:00
/// how many signals to handle before exiting
const STOP_AFTER: u64 = 10;
2019-07-03 10:40:59 -07:00
#[tokio::main]
async fn main() {
// tokio_signal provides a convenience builder for Ctrl+C
// this even works cross-platform: linux and windows!
//
// `CtrlC::new()` produces a `Future` of the actual stream-initialisation
2019-07-03 10:40:59 -07:00
// so first we await until the signal is ready.
let endless_stream = tokio_signal::CtrlC::new().await.unwrap();
// don't keep going forever: convert the endless stream to a bounded one.
let mut limited_stream = endless_stream.take(STOP_AFTER);
// how many Ctrl+C have we received so far?
let mut counter = 0;
2016-09-08 17:13:18 -07:00
2018-05-03 19:12:23 +02:00
println!(
"This program is now waiting for you to press Ctrl+C {0} times. \
Terminate by repeating Ctrl+C {0} times, or ahead of time by opening \
a second terminal and issuing `pkill -sigkil ctrl-c`.",
2018-05-03 19:12:23 +02:00
STOP_AFTER
);
// Up until now, we haven't really DONE anything, just prepared
// our futures, now it's time to actually await the results!
while let Some(_) = limited_stream.next().await {
// Note how we manipulate the counter without any fancy synchronisation.
// The borrowchecker realises there can't be any conflicts, so the closure
// can just capture it.
counter += 1;
println!(
"Ctrl+C received {} times! {} more before exit",
counter,
STOP_AFTER - counter
);
}
println!("Stream ended, quiting the program.");
2016-09-08 17:13:18 -07:00
}