m06-error-handling

Choose Result for expected recoverable failures, Option for absent values, and panic only for unrecoverable contract violations. Design error types with thiserror to propagate typed errors across library boundaries, and use anyhow to add application-level context for user-facing messages.

Use thiserror to define typed error enums for library APIs, and use anyhow to handle dynamic application errors with added context. This separation keeps library boundaries explicit while simplifying application-level error propagation and user-facing surface messages.

Add context to Rust errors by wrapping the underlying std::error::Error source during propagation. Use anyhow's context methods to attach meaningful application-level messages, ensuring the user-facing output clearly explains the failure path across crate boundaries.

Use panic in Rust for unrecoverable contract violations or unreachable code, and use Result for expected recoverable failures. Reserve typed errors and Result propagation for expected operational failures to maintain robust library design and application stability.

Yes, the Skill guides refactoring failing Rust functions to use typed errors, add context, and implement clear error paths. It applies patterns for error propagation and source wrapping to real-world Rust projects using thiserror and anyhow.