• Sources: primary, discussion
  • Summary: The guide adds rules on top of the public Rust style guide to make large-scale automated changes easier, such as no glob imports, one module per use statement, and module-qualified function calls. It advises avoiding Rc and Arc, preferring enums over bool parameters, and expect over unwrap. Some rules are Chromium-specific, including small crates, flat file layout, and no async or std thread spawning.
  • Why it matters: Teams setting Rust conventions for large monorepos get a tested baseline with rationale for each rule.