fix: Use a different std::thread::Thread for Stdin IO

[vrongmeal]

See: https://docs.rs/tokio/latest/tokio/io/struct.Stdin.html

This handle is best used for non-interactive uses, such as when a
file is piped into the application. For technical reasons, stdin is
implemented by using an ordinary blocking read on a separate thread,
and it is impossible to cancel that read. This can make shutdown of
the runtime hang until the user presses enter.

For interactive uses, it is recommended to spawn a thread dedicated to
user input and use blocking IO directly in that thread.

Resolves: #61

[infiniteregrets]

I made a change to use std::process::exit as normal return Ok(()) wouldnt work.. maybe that can changed back to normal now?

[vrongmeal]

I made a change to use std::process::exit as normal return Ok(()) wouldnt work.. maybe that can changed back to normal now?

Oh yeah, should be. Which change is this BTW? I'll revert it.

[infiniteregrets]

Oh yeah, should be. Which change is this BTW? I'll revert it.

can't find it, but can you just try breaking from the loop and do return Ok(()). try it with the starwars example, and see if the process exits on ctrl+C

[infiniteregrets]

thanks for finding and fixing this!