> Relative to this, unwrapping is perfectly acceptable in application code. Unwrapping may be acceptable in application code - it depends on your application.

> Relative to this, unwrapping is perfectly acceptable in application code. Unwrapping may be acceptable in application code - it depends on your application. Specifically it depends on whether you need specific handling of unexpected events. If your program is a 'script' - by which I mean something that executes for a short period of time to perform a series of tasks and then exits - then panicking on an error is a reasonable way of aborting. On the other hand, if it's a daemon, then you will likely want to gracefully handle all error conditions and carry on. I think the issue here is that Rust is primarily used as a systems programming language and usage tends more to fall in the 'daemon' category. In that mentality you handle every error (even if it's just to print something), and that is probably where the general community pointers towards avoiding unwrap come from.