commit 003b607d7b8e3d478f05ca6ec9ff6b7fc1a29260
author Lukasz Anforowicz <lukasza@chromium.org> Sat May 17 01:16:33 2025
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Sat May 17 01:16:33 2025
tree 808f65cb22ef8cc6f6947d5952de4deacafebb4a
parent 953754490340d7325049d5a90faae7d44d1435e6

[rust] Use `-Awarnings` instead of `--cap-lints=allow`.

Before this CL warnings under `//third_party/rust` have been suppressed
using `--cap-lints=allow`.  This didn't allow to selectively re-enable
some warnings (e.g. the ones behind `//build/rust:forbid_unsafe` or
`//build/config/compiler:disallow_unstable_features`).

After this CL warnings under `third_party/rust` are suppressed using a
combination of:

* `-Awarnings`
* Avoiding transitively pulling in
  `//build/config/compiler:default_warnings` and
  `//build/config/compiler:treat_warnings_as_errors` via
  `//build/config/compiler:no_chromium_code`.

This CL helps with:

* Actually enforcing `disallow_unstable_features` for
  `//third_party/rust`.  This required tweaking `bytemuck`'s config in
  this CL to declare which unstable features are needed.
* Unblocking a follow-up CL where we start enforcing
  `allow_unsafe = false` for `cargo_crate` targets.  See the WIP CL at
  https://crrev.com/c/6538666.

This CL has been generated semi-automatically:

* `third_party/rust/chromium_crates_io/BUILD.gn.hbs` and
  `build/rust/cargo_crate.gni `have been edited manually.
* `BUILD.gn` files have been regenerated by running
  `tools/crates/run_gnrt.py gen`

Bug: 399931417
Change-Id: I2954ffacfe45ddcbaf596d6f4172437764b47fa8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6538606
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1461703}