🗂️ interruptible

Crates.io docs.rs CI Coverage Status

Stops a future producer or stream from producing values when an interrupt signal is received.

For a future that returns either Result<T, ()> or ControlFlow<T, ()>, calling fut.interruptible_*(tx) causes the returned value to be Err(()) or Break(T) if an interruption signal is received while that future is executing.

This means the future is progressed to completion, but the return value signals the producer to stop yielding futures.

For a stream, when the interrupt signal is received, the current future is run to completion, but the stream is not polled for the next item.

Usage

Add the following to Cargo.toml

```toml interruptible = "0.0.1"

Enables:

#

* InterruptibleFutureExt::{interruptible_control_ctrl_c, interruptible_result_ctrl_c}

* InterruptibleStreamExt::interruptible_ctrl_c if the "stream" feature is also enabled.

interruptible = { version = "0.0.1", features = ["ctrl_c"] }

Enables InterruptibleStreamExt

interruptible = { version = "0.0.1", features = ["stream"] } ```

Code

Future<Output = ControlFlow<B, C>>

```rust use std::ops::ControlFlow;

use futures::FutureExt; use tokio::{join, sync::oneshot};

use interruptible::{InterruptSignal, InterruptibleFutureExt};

[tokio::main]

async fn main() { let (interrupttx, interruptrx) = oneshot::channel::(); let (readytx, readyrx) = oneshot::channel::<()>();

let interruptible_control = async {
    let () = ready_rx.await.expect("Expected to be notified to start.");
    ControlFlow::Continue(())
}
.boxed()
.interruptible_control(interrupt_rx);

let interrupter = async move {
    interrupt_tx
        .send(InterruptSignal)
        .expect("Expected to send `InterruptSignal`.");
    ready_tx
        .send(())
        .expect("Expected to notify sleep to start.");
};

let (control_flow, ()) = join!(interruptible_control, interrupter);

assert_eq!(ControlFlow::Break(InterruptSignal), control_flow);

} ```

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.