Can it help me unify different error types in a single function?

Yes, it offers specific patterns for creating unified error enums that allow the '?' operator to automatically convert various error sources.

When should I use 'anyhow' instead of custom error enums?

The skill provides guidance on using anyhow for application-level flexibility and custom enums for library-level type safety and specific error matching.

Does this skill support manual From trait implementations?

Yes, it includes patterns for manual implementations when you need custom logic to map external errors to internal domain variants.

How does this skill help with the 'thiserror' crate?

It provides code templates and architectural patterns for using the #[from] and #[error] macros to automate boilerplate error conversion.

Rust Error Handling Guide

Name: Rust Error Handling Guide
Author: EmilLindfors

byEmilLindfors

Learning & Documentation

Implements idiomatic Rust error conversion patterns and From trait implementations to simplify complex error handling logic.

About

This skill empowers developers to master Rust's error handling ecosystem by providing expert guidance on converting between error types. It provides implementation patterns for the From trait, integrates with crates like thiserror and anyhow, and offers best practices for designing error boundaries in layered architectures. Whether you are unifying multiple error types using the '?' operator or refactoring manual map_err calls into clean enum variants, this guide ensures your Rust code remains robust, idiomatic, and maintainable.

Key Features

0 GitHub stars
Layered architecture patterns for converting infrastructure errors to domain errors
Automatic From trait implementation suggestions using thiserror patterns
Standardized patterns for unifying multiple error types within a single Result
Guided implementation of error type aliases for cleaner function signatures
Best practices for using anyhow and Boxed errors in flexible applications

Use Cases

Creating a centralized application error enum to aggregate IO, Database, and API errors
Refactoring manual map_err chains into idiomatic automatic conversions using #[from]
Implementing custom conversion logic for external crate errors into domain-specific types

About

Key Features

0 GitHub stars
Layered architecture patterns for converting infrastructure errors to domain errors
Automatic From trait implementation suggestions using thiserror patterns
Standardized patterns for unifying multiple error types within a single Result
Guided implementation of error type aliases for cleaner function signatures
Best practices for using anyhow and Boxed errors in flexible applications

Use Cases

Creating a centralized application error enum to aggregate IO, Database, and API errors
Refactoring manual map_err chains into idiomatic automatic conversions using #[from]
Implementing custom conversion logic for external crate errors into domain-specific types