When I Ctrl+C on cargo run and my Rust program is set up to intercept the signal, the Cargo process stops and returns control to the terminal, even though my Rust program may still be running. I've observed this on latest nightly.
I think it would be best for cargo run to also intercept Ctrl+C when running a program, and ignore it – instead, it should just check regularly to see if the program it's running has exited. This would certainly be a more reliable approach.
When I Ctrl+C on
cargo runand my Rust program is set up to intercept the signal, the Cargo process stops and returns control to the terminal, even though my Rust program may still be running. I've observed this on latest nightly.I think it would be best for
cargo runto also intercept Ctrl+C when running a program, and ignore it – instead, it should just check regularly to see if the program it's running has exited. This would certainly be a more reliable approach.