Running commands#

Use cargo fc as if it were cargo. The command and its arguments are forwarded to each combination’s invocation:

cargo fc check
cargo fc clippy
cargo fc build
cargo fc test
cargo fc doc

Forwarded arguments#

Every cargo argument is passed through except the three that would conflict with the matrix cargo fc builds for you:

--features
--all-features
--no-default-features

Everything else is forwarded verbatim, so this works as expected:

cargo fc check -p my-crate --all-targets
cargo fc test --release -- --nocapture

Arguments after -- are passed to the invoked program (for example the test binary), never interpreted by cargo fc.

Package selection#

In a workspace, cargo fc runs the selected packages. Use cargo’s own selection flags:

# One package
cargo fc check -p engine

# The whole workspace, excluding one package
cargo fc check --workspace --exclude examples

--exclude is accepted for Cargo-compatible workspace selection. You can also exclude packages permanently in workspace metadata — see Configuration basics.

Toolchains#

A leading +toolchain works exactly like it does with cargo:

cargo fc +nightly check

The toolchain is forwarded to every invocation. When cargo fc installs missing target components (see Installing targets), it passes the same override to rustup.

Built-in commands and aliases#

cargo fc recognizes these built-in cargo commands, including their short aliases: build (b), check (c), clippy, doc (d), test (t), and run (r). Recognized commands automatically gain capabilities such as configured targets.

cargo fc also resolves aliases from your .cargo/config.toml before running. If an alias expands to a built-in, it inherits that built-in’s behavior:

# .cargo/config.toml
[alias]
lint = "clippy --all-targets --no-deps"

# Behaves like `cargo fc clippy`
cargo fc lint

A custom command that does not resolve to a built-in runs across the matrix all the same, but you must opt in explicitly to give it target or diagnostics capabilities. See Per-command configuration.

Pointing at another project#

For local development you can inspect a manifest elsewhere:

cargo run -- cargo check --manifest-path ../other/Cargo.toml
cargo run -- cargo matrix --manifest-path ../other/Cargo.toml --pretty