Order rust lints before clippy lints to allow ignoring unknown lints (#4030)

When updating the Rust toolchain in a quickly moving repository, it can
be difficult to atomically fix all the lints and update the toolchain in
a single commit. It can be helpful to:

* land a patch that adds the flags `-Aunknown_lints
-Aclippy::useless_borrows_in_formatting`. Rust needs them in that order,
otherwise it will error out.
* land the toolchain update.
* clean up the remaining lint failures.

Unfortunately before this patch rules_rust would emit the clippy lints
first, then the rustc lints, so we couldn't use this pattern. This patch
reverses the order and fixes this issue.

Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
1 file changed
tree: d478611bda6643b444d50b48425d661490cccc06
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cargo/
  5. crate_universe/
  6. docs/
  7. examples/
  8. extensions/
  9. ffi/
  10. nix/
  11. rust/
  12. test/
  13. tools/
  14. util/
  15. .bazelignore
  16. .bazelrc
  17. .clang-format
  18. .clippy.toml
  19. .envrc
  20. .gitattributes
  21. .gitignore
  22. .pre-commit-config.yaml
  23. .prettierrc.toml
  24. .rustfmt.toml
  25. .typos.toml
  26. ARCHITECTURE.md
  27. AUTHORS
  28. BUILD.bazel
  29. CODEOWNERS
  30. COMPATIBILITY.md
  31. CONTRIBUTING.md
  32. CONTRIBUTORS
  33. LICENSE.txt
  34. MODULE.bazel
  35. README.md
  36. version.bzl
  37. WORKSPACE.bazel
README.md

Rust Rules

  • Postsubmit Build status

Overview

This repository provides rules for building Rust projects with Bazel.

Starter repo

The fastest way to try this in an empty project is to click the green “Use this template” button on https://github.com/bazel-starters/rust.

Community

General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.

Documentation

Please refer to the full documentation.