rust-coding-guidelines

Standardize Rust GPUI coding by enforcing explicit error propagation and discouraging unwraps. You must propagate errors with meaningful messages and document any exceptions in code comments and commit messages to ensure robust code.

Standardize Rust GPUI modules by following prescribed naming conventions, code layout, and file organization rules. Applying these structural guidelines when starting new modules aligns your code with project reviews and streamlines team collaboration.

Structure async patterns in Rust GPUI applications by applying standardized async coding guidelines. Following these prescribed patterns ensures code maintainability and aligns your asynchronous logic with project review standards.

These Rust coding guidelines apply specifically to GPUI work and enforce explicit error handling alongside GPUI-specific rules. While they cover general Rust standards, they are tailored for GPUI project reviews and maintainability.

Document exceptions to Rust error propagation rules in code comments and commit messages whenever exceptions are necessary. This practice maintains robust code and clarifies the rationale for bypassing explicit error handling during project reviews.