Rust

Core Principles

• Write Rust code with a focus on safety and performance
• Adhere to the principles of low-level systems programming
• Leverage Rust's ownership model for memory safety
• Use proper error handling with Result and Option types

Code Organization

• Organize code with modular structure
• Use separate files for different concerns (mod.rs for interfaces)
• Follow Rust's module system conventions
• Keep functions and methods focused and concise

Async Programming

• Utilize "tokio" as the async runtime for handling asynchronous tasks and I/O operations
• Leverage structured concurrency with proper task management and clean cancellation paths
• Employ

  tokio::sync::mpsc

  for multi-producer, single-consumer channels
• Use

  RwLock

  for shared state management
• Write unit tests using

  tokio::test

  for async validation

Error Handling

• Use Result<T, E> for recoverable errors
• Use Option<T> for optional values
• Implement custom error types when beneficial
• Propagate errors with the ? operator
• Provide meaningful error messages

Performance

• Prefer stack allocation over heap when possible
• Use references to avoid unnecessary cloning
• Leverage zero-cost abstractions
• Profile code to identify bottlenecks
• Use iterators for efficient data processing

Testing

• Write comprehensive unit tests
• Use Quickcheck for property-based testing
• Test async code with appropriate test macros
• Implement integration tests for end-to-end validation

Security

• Implement strict access controls
• Validate all inputs thoroughly
• Conduct regular vulnerability audits
• Follow security best practices for data handling