rust-best-practices

Rust error handling best practices dictate using thiserror for libraries to define custom error types and anyhow for applications to simplify dynamic error propagation. This approach ensures robust, context-rich error management across your crate boundaries.

Rust API design best practices promote the builder pattern for complex object construction and newtype wrappers for type safety. These patterns prevent invalid states, improve ergonomics, and enforce clear abstraction boundaries within your codebase.

Refactoring a Rust crate for testability and async performance involves applying structured best practices to avoid anti-patterns. This Skill provides guardrails to guide async patterns, testing strategies, and performance optimizations for robust projects.

Yes, avoiding anti-patterns is a core feature of Rust best practices. It provides explicit guardrails and actionable patterns to identify and prevent common pitfalls, ensuring your code remains reliable, safe, and idiomatic throughout development.

You need thiserror and anyhow for robust Rust error handling when building libraries and applications respectively. Thiserror creates structured library errors while anyhow aggregates application-level errors, ensuring explicit and reliable error propagation.

Aligning your Rust function with best practices involves applying structured guidelines for error handling, API design, and performance. Enforcing thiserror, anyhow, builder patterns, and newtypes ensures safer, more idiomatic code.