m06-error-handling

Rust error handling with Result and Option requires choosing between recoverable errors and optional values. Use Result for fallible operations like IO or parsing, and Option when a value may be absent without indicating a failure.

Use panic in Rust for unrecoverable states or violated invariants, and return a Result for expected recoverable failures like IO errors or parsing failures. Correct panic versus return strategies ensure robust domain error propagation across application layers.

Propagating errors with context in Rust is best achieved using thiserror for typed library errors and anyhow for application-level error chains. This combination provides ergonomic error handling and rich contextual messages across architectural layers.

Designing typed error enums in Rust involves defining custom error types using thiserror, implementing source chaining to wrap underlying causes, and creating ergonomic error handling across library, service, and application layers for improved debuggability.

Yes, thiserror works well for domain-specific error propagation by enforcing typed errors with contextual messages. It integrates effectively across library and application codebases to handle IO, parsing, and domain-specific errors with structured source chaining.