rust-polyglot-conventions

Enforce Rust coding standards by applying conventions that mandate PascalCase for types, snake_case for functions, and robust error handling using `Result<T, Error>` with the `?` operator to avoid `.unwrap()` in production.

Best practices for async operations in Rust promote using Tokio as the async runtime and providing `_sync` wrappers to ensure robust asynchronous patterns and maintain code flexibility across different execution contexts.

Ensure Rust code passes clippy with zero warnings by enforcing `cargo clippy -- -D warnings` to guarantee that all new code adheres to established project guidelines for maintainability and high code quality.

Manage memory in Rust by using `Arc` for shared ownership and `Mutex` or `RwLock` for interior mutability, and optimize performance by utilizing `ahash` for HashMaps along with `lazy_static` or `once_cell`.

These Rust conventions are applicable to software engineering projects requiring high code quality and maintainability, ensuring that both new and existing codebases adhere to idiomatic Rust standards.