From 687226e9c14970e98cccd919753983851c509390 Mon Sep 17 00:00:00 2001 From: L3Sota Date: Tue, 12 Aug 2025 16:54:21 +0900 Subject: [PATCH] fix(post-01): typo --- .../edition-2/posts/01-freestanding-rust-binary/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/edition-2/posts/01-freestanding-rust-binary/index.md b/blog/content/edition-2/posts/01-freestanding-rust-binary/index.md index 80ee5e16..628aa76d 100644 --- a/blog/content/edition-2/posts/01-freestanding-rust-binary/index.md +++ b/blog/content/edition-2/posts/01-freestanding-rust-binary/index.md @@ -583,7 +583,7 @@ bench = false The double-brackets around `bin` are not a mistake, this is how the TOML format defines keys that can appear multiple times. Since a crate can have multiple binaries, the `[[bin]]` section can appear multiple times in the `Cargo.toml` as well. -This is also the reason for the mandatory `name` field, which needs to match the name of the binary (so that `cargo` knows which settings should be applied to whick binary). +This is also the reason for the mandatory `name` field, which needs to match the name of the binary (so that `cargo` knows which settings should be applied to which binary). By setting the [`test`](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-test-field) and [`bench` ](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-bench-field) fields to `false`, we instruct `cargo` to not build our binary in test or benchmark mode. Now `cargo check --all-targets` should not throw any errors anymore, and the `checkOnSave` implementation of `rust-analyzer` should be happy too.