coding-guidelines

To fix common Rust clippy lints, apply concrete remediation mappings that replace deprecated patterns like try! with ? and lazy_static with OnceLock. This enforces idiomatic Rust code and resolves review friction across team projects.

Rust naming and formatting best practices involve following clear conventions for lifetimes, variables, and documentation to improve readability. Using rustfmt ensures consistent code style, making source code more maintainable across libraries and applications.

To enforce Rust async and error handling guidelines, establish a project-level style guide that defines safe concurrency patterns and error propagation rules. This ensures consistent handling of asynchronous operations and safe error management across the codebase.

Yes, this Rust style guidance works for both libraries and applications. It provides concise, opinionated coding conventions applicable to various source code scenarios, including refactoring, code reviews, and establishing project-level style enforcement.

You should modernize your Rust codebase to replace lazy_static with OnceLock when addressing clippy lint warnings during refactoring. Mapping legacy patterns to modern standard library equivalents reduces dependency overhead and aligns with current idiomatic Rust practices.