| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
To opt into running Clippy, please set `enable_rust_clippy = true` in `args.gn`.
With this `args.gn` setting building a 1st-party Rust library will also
invoke Clippy.
Clippy is disabled by default to avoid adding build overhead to
Chromium engineers primarily working with C, C++, or Java.
Engineers working on 1st-party Rust code in Chromium
should consider setting `enable_rust_clippy = true` in their `args.gn`,
but this is optional.
Without this opt-in potential Clippy issues in one's CLs
won’t be detected until a CQ pass.
Additionally, this opt-in is required
to locally repro, fix, and verify Clippy errors (if any).I think we can be stronger here; people _really really should_ be enabling clippy locally if they're doing rust work.
```suggestion
When building locally, Clippy is disabled by default to avoid adding build overhead to Chromium engineers primarily working with C, C++, or Java.
However, Clippy warnings are enforced by the CQ. Therefore, it is strongly recommended that engineers working with Rust code enable Clippy warnings by setting `enable_rust_clippy = true` in their `args.gn`.
Doing so allows you to fix Clippy warnings as they occur, rather than waiting to discover them until after uploading a CL. It also lets you verify that you've fixed all the problems when rebuilding locally.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |