Rust Development

House style for every Rust change, however small.

Process:

1. Read references/style-and-design.md once per session before the first Rust edit
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
5. When the file is fully compliant, add a comment: // Rust guideline compliant {date} where {date} is the guideline date/version

Non-negotiables (see references for detail)

1. Panics mean "stop the program". Panic only on programming errors and poisoned locks; return Result for situational failures. Never introduce an Error type for contract violations.
2. unsafe implies UB. Mark a function unsafe only when misuse can cause undefined behavior; every unsafe block carries a Safety doc section listing caller obligations. Prefer safe APIs (e.g., windows crate wrappers) over raw FFI.
3. No weasel words. No Manager/Service/Factory types; name by what the type does (Bookings, BookingDispatcher); Builder is the canonical factory.
4. Windows API and FFI work follows the ms-win32 skill — it owns the Win32 correctness, FFI declaration, and DLL-boundary rules. Load it alongside this one; its rules are deliberately not restated here.