Rust Development

House style for Rust changes. A codebase with its own established conventions wins on style — match the surrounding code there. Correctness rules do not bend to local habit: platform rules (ferris-windows), error discipline, and unsafe obligations apply even where the surrounding code violates them.

Process:

1. Before the first Rust edit, read the sections of references/style-and-design.md that govern the change — naming and error discipline always; documentation, unsafe/FFI, dependency, async, or performance sections when the change touches them
2. Make every new or modified line conformant
3. Document every public item with M-CANONICAL-DOCS sections (Examples/Errors/Panics/Safety/Abort when applicable)
4. Write comments in American English unless the user explicitly requests another language

Non-negotiables (see references for detail)