Skip to content

Use cargo check instead of build - #514

Closed
c-x-berger wants to merge 1 commit into
actions:masterfrom
c-x-berger:patch-1
Closed

c-x-berger wants to merge 1 commit into
actions:masterfrom
c-x-berger:patch-1

Conversation

@c-x-berger

@c-x-berger c-x-berger commented May 17, 2020 •

Copy link
Copy Markdown

cargo check is usually faster than cargo build, but for the purposes of testing if code compiles, has the same effect.

The results of cargo check are cached for use by other Cargo subcommands (e.g. cargo build), so the run will fail faster, but succeed in more-or-less the same amount of time.

[`cargo check`](https://doc.rust-lang.org/cargo/commands/cargo-check.html) is often noticeably faster than `cargo build`, but for the purposes of testing if code compiles, has the same effect.

The results of `cargo check` are cached for use by `cargo build`, so the run will _fail_ faster, but succeed in more-or-less the same amount of time.
@c-x-berger

Copy link
Copy Markdown
Author

Wait, no, cargo build fails in the same amount of time.

I'm real smart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant