Awesome Reviewers

Verification · Static analysis · Type checking

Compiler as checker

In compiled languages the build is the type check; a failing build is this check failing.

How to build it

  1. Make the build step in CI the gate for type errors in compiled code.
  2. Run cargo check on pull requests for a fast type-only pass.
  3. Keep compiler warnings as errors in CI so type issues stop the pipeline.

Signals in a repository

  • A CI job that runs cargo build or cargo check and fails the pipeline on error.
  • Compiler flags such as -Werror or RUSTFLAGS set in CI configuration.

In practice

21 repositories run a tool for this check in the scanned set.

  • cargo-check · 21 repos

Examples

  • facebook/react · cargo-check

    cargo check

  • oven-sh/bun · cargo-check

    cargo check --workspace --all-targets --keep-going

  • warpdotdev/warp · cargo-check

    cargo check --locked -p warp --lib --features agent_mode_evals

  • aaif-goose/goose · cargo-check

    cargo check --locked --target wasm32-unknown-unknown -p goose-agent -p goose-provider-types

  • ruvnet/ruflo · cargo-check

    cargo check --features native --verbose