Don't crash on I/O errors

This does mean an I/O error is now considered a negative response (since exit code 1 will be returned). I think that's ok.

Signed-off-by: Alex Saveau <[email protected]>

Author: SUPERCILEX

src/main.rs

@@ -12,15 +12,15 @@ fn main() -> impl Termination {
 
         let mut stdin = ManuallyDrop::new(unsafe { File::from_raw_fd(0) });
         let mut stdout = ManuallyDrop::new(unsafe { File::from_raw_fd(1) });
-        ask(question, &mut *stdin, &mut *stdout).unwrap()
+        ask(question, &mut *stdin, &mut *stdout)
     }
     #[cfg(not(unix))]
     {
         use std::io;
 
         let mut stdin = io::stdin().lock();
         let mut stdout = io::stdout().lock();
-        ask(&question, &mut stdin, &mut stdout).unwrap()
+        ask(&question, &mut stdin, &mut stdout)
     }
 }