From 096b099e92061cfd952c62c9ba83ed3ebe840382 Mon Sep 17 00:00:00 2001
From: EuAndreh <eu@euandre.org>
Date: Mon, 5 Oct 2020 18:02:12 -0300
Subject: cargo2nix: Proofread on the browser
---
...05-cargo2nix-dramatically-simpler-rust-in-nix.md | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md b/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md
index a799ff4..a7d6850 100644
--- a/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md
+++ b/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md
@@ -47,20 +47,21 @@ in pkgs.stdenv.mkDerivation {
```
That `cargo test` part on line 20 is what I have been fighting with every
-"\*2nix" available for Rust out there. I don't want to bash any of them, all I
+"\*2nix" available for Rust out there. I don't want to bash any of them. All I
want is to have full control of what Cargo commands to run, and the "*2nix" tool
-should only setup the environment for me. Just let me run Cargo however I want,
-no need to parameterize how the tool runs Cargo for me, or even replicate Cargo
+should only setup the environment for me. Let me run Cargo however I want, no
+need to parameterize how the tool runs Cargo for me, or even replicate Cargo
commands by calling the Rust compiler directly.
-Sure it doesn't support private registries or Git dependencies, but how
-much bigger does it has to be to support it? Also, it doesn't support those
-**yet**, there's no reason why for extending it to support them. I just haven't
-needed it yet, so I haven't added. Patches welcome.
+Sure it doesn't support private registries or Git dependencies, but how much
+bigger does it has to be to support it? Also, it doesn't support those **yet**,
+there's no reason it can't be extended to support them. I just haven't needed it
+yet, so I haven't added. Patches welcome.
-The layout of the `vendor/` directory is more explicit and public: whatever the
-command `cargo vendor` returns. However I haven't checked if the shape of the
-`.cargo-checksum.json` is specified, or internal to Cargo.
+The layout of the `vendor/` directory is more explicit and public then what
+swift2nix does: it is whatever the command `cargo vendor` returns. However I
+haven't checked if the shape of the `.cargo-checksum.json` is specified, or
+internal to Cargo.
Try out the demo (also taken from the repo's README):
--
cgit v1.2.3