A Rust style rule can be sensible in Chromium and a poor fit for a small Cargo application. The useful detail in Google's Rust guide is that it tells you where some rules belong. 🔍

The guide drew a fresh Hacker News discussion on October 21. I read it as a set of decisions for particular codebases, rather than a replacement for every Rust project's conventions. [1][2]

My reading aid for applying the guide. The guide itself is the authority for each rule's exact scope.

A label changes the advice

Google explains that consistency helps tooling make changes across large codebases. Some recommendations are explicitly marked for Chromium or Fuchsia. Its Chromium file-layout guidance also distinguishes that build environment from conventional Cargo layout. [1]

That is useful context before a review comment becomes “Google says this is wrong.” 🧭

Suppose a project already has a clear Cargo module structure and a contribution guide.…