rust-best-practices

Idiomatic Rust borrowing versus ownership guidelines provide structured patterns to improve safety and readability. These ergonomic code patterns help developers choose between borrowing and owning data effectively during code reviews and library design.

Rust error handling strategies using Result, thiserror, and anyhow provide structured approaches to manage failures safely. These practices ensure maintainable API design while improving error propagation and readability across Rust projects.

Performance-minded Rust practices for generics and cloning reduce unnecessary overhead and improve execution speed. These guidelines address efficient generic constraints and cloning behaviors to enhance overall application performance.

Rust testing and linting best practices are included to improve safety and code quality. The guidelines cover testing-focused documentation and linting configurations to ensure maintainable and reliable Rust codebases.

Rust documentation guidelines aligned with rustdoc conventions ensure clear and maintainable code references. These practices provide living examples and structured documentation to improve readability and library design.

Rust best practices for library design and code reviews are needed when improving safety, readability, and performance. These guidelines apply idiomatic patterns to evaluate borrowing, error handling, generics, and documentation effectively.