cargo-check --- Check the current package
cargo check
[options]
Check a local package and all of its dependencies for errors. This will essentially compile the packages without performing the final step of code generation, which is faster than running cargo build
. The compiler will save metadata files to disk so that future runs will reuse them if the source has not been modified. Some diagnostics and errors are only emitted during code generation, so they inherently won't be reported with cargo check
.
By default, when no package selection options are given, the packages selected depend on the selected manifest file (based on the current working directory if --manifest-path
is not given). If the manifest is the root of a workspace then the workspaces default members are selected, otherwise only the package defined by the manifest will be selected.
The default members of a workspace can be set explicitly with the workspace.default-members
key in the root manifest. If this is not set, a virtual workspace will include all workspace members (equivalent to passing --workspace
), and a non-virtual workspace will include only the root crate itself.
When no target selection options are given, cargo check
will check all binary and library targets of the selected packages. Binaries are skipped if they have required-features
that are missing.
Passing target selection flags will check only the specified targets.
Note that --bin
, --example
, --test
and --bench
flags also support common Unix glob patterns like *
, ?
and []
. However, to avoid your shell accidentally expanding glob patterns before Cargo handles them, you must use single quotes or double quotes around each glob pattern.
The feature flags allow you to control which features are enabled. When no feature options are given, the default
feature is activated for every selected package.
See the features documentation for more details.
See the reference for details on environment variables that Cargo reads.
0
: Cargo succeeded.101
: Cargo failed to complete.Check the local package for errors:
cargo check
Check all targets, including unit tests:
cargo check --all-targets --profile=test