rust-coding-style

To enforce idiomatic Rust coding standards for a database project, apply specific rules for code organization, prefer iterator chains over mutable accumulators, and use designated macros for struct field definitions to ensure consistency.

The best way to refactor Rust code to use iterator chains is to replace mutable accumulators with functional iterator methods like .fold() and .map(), creating cleaner and more maintainable code.

To organize helper functions in idiomatic Rust code, merge them directly into their owning structs and convert them into private methods, reducing scattered standalone functions and improving structural encapsulation.

You should use macros for struct field definitions in Rust when working with fixed-offset fields, utilizing specific macros like page_field! and tuple_field! to maintain a single source of truth for field layouts.

This Rust refactoring guidance applies specifically to the PepperDB project repository, enforcing strict coding conventions for all Rust code development and refactoring tasks within that particular codebase.

You should prefer iterator chains over mutable accumulators in Rust because functional patterns like .map() and .fold() reduce cognitive load, yield cleaner code, and improve overall project maintainability.