The codebase contains 233+ expect(), unwrap(), and panic!() calls that could cause the application to crash. Many of these are in production code paths where errors should be handled gracefully.
| Crate | Severity | Examples |
|-------|----------|----------|
| chicken_network | High | Certificate generation, socket binding |
| chicken_settings | Medium | File operations, serialization |
| chicken_steam | Medium | Steam API initialization |
| chicken_polygon | Low | Geometry operations |
// Network - could crash on startup
.expect("all given SANs should be valid DNS names");
.expect("should be a valid certificate");
.expect("failed to bind discovery socket");
// Settings - could crash on file operations
.unwrap(); // 15+ occurrences in settings_edit
// Steam - could crash if Steam not running
.expect("Some error occurred");
Result and propagate errors to callerthiserror or anyhow for context-rich errorsexpect()/unwrap() calls in production codeanyhow or thiserror#![warn(clippy::unwrap_used)] enabled