m06-error-handling

Design Rust error types for a library using thiserror by defining strong, typed error variants that represent domain-specific failures. This approach ensures clear, structured error propagation across module boundaries and enables ergonomic handling for consumers.

Use anyhow for application-level error handling to add rich context dynamically, and use thiserror for library design to expose structured, typed errors. This separation ensures ergonomic user-facing messages while maintaining strict type safety for library consumers.

The best way to propagate context across module boundaries in Rust is using anyhow::Context to attach rich messages and proper source chaining. This strategy maintains the full error stack trace across different layers of an application.

Convert between Option and Result in Rust error handling using pattern guidance to map None values to specific error types. This ensures robust error propagation by explicitly defining how missing values translate into structured failures.

Return Result for expected, recoverable errors in Rust libraries to allow callers to handle failures gracefully, and reserve panics for unrecoverable state violations. This strategy ensures robust domain-driven error design and safe module boundaries.

Yes, this Rust error handling skill applies to both library and application code. It provides pattern guidance for defining domain-driven error types and ergonomic user-facing messages across different architectural boundaries.