handling-rust-errors

Standardize Rust error handling by applying the error-stack pattern to unify error creation and propagation. This approach uses derive_more to define error types and implement the Error trait for consistent formatting across library boundaries.

Propagate Rust errors across async boundaries using error-stack's change_context and ResultExt. These tools maintain consistent error context and stack traces seamlessly when propagating through asynchronous functions and library boundaries.

Add contextual information to Rust errors using error-stack's attach method. This augments wrapped upstream errors with extra context during propagation, improving debuggability and maintainability throughout the codebase.

derive_more works with error-stack by generating the Error trait implementation for small error enums. This ensures consistent error formatting while allowing change_context to handle type conversions during error propagation.

Yes, you can document Rust error variants using the error-stack pattern. The approach incorporates intra-doc links and examples directly within error type definitions to clearly document usage and error conditions.

Use change_context instead of standard error conversion in Rust because it preserves the original error stack while wrapping it in a new error type. This maintains debuggability across library boundaries better than simple From implementations.