From 8566e595832e5c6ee3f5131ac497a2aaed697a46 Mon Sep 17 00:00:00 2001 From: Melody Horn Date: Tue, 29 Sep 2020 16:04:50 -0600 Subject: minor accuracy boost --- _posts/2020-09-28-crowbar-1-defining-a-c-replacement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '_posts') diff --git a/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md b/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md index bdbd96b..f7be6a1 100644 --- a/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md +++ b/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md @@ -3,7 +3,7 @@ title: "Crowbar: Defining a good C replacement" --- I like Rust a lot. -That said, the always-opinionated, often-correct Drew DeVault raises some good points in his blog post [Rust is not a good C replacement](https://drewdevault.com/2019/03/25/Rust-is-not-a-good-C-replacement.html). +That said, the always-opinionated, ~~often-correct~~ [occasionally-correct](https://cmpwn.com/@sir/104946211496582150) Drew DeVault raises some good points in his blog post [Rust is not a good C replacement](https://drewdevault.com/2019/03/25/Rust-is-not-a-good-C-replacement.html). He names some attributes that C has and Rust lacks which he thinks are required in a good C replacement. So what can we say are some features of a hypothetical good C replacement? -- cgit v1.2.3