From 2c9bfa244e8eb093ce4f3288649156771c51d5d8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C4=B0smail=20Ar=C4=B1l=C4=B1k?= Date: Mon, 10 Jul 2023 15:54:06 +0300 Subject: [PATCH] Improve cleanup-crew.md with an example post Add a post which explains how to use C-reduce with Rust in cleanup-crew.md --- src/notification-groups/cleanup-crew.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/notification-groups/cleanup-crew.md b/src/notification-groups/cleanup-crew.md index 9850b3d06..707334304 100644 --- a/src/notification-groups/cleanup-crew.md +++ b/src/notification-groups/cleanup-crew.md @@ -41,7 +41,7 @@ are a few: code automatically. * The [C-reduce](https://github.com/csmith-project/creduce) tool also works on Rust code, though it requires that you start from a single - file. (XXX link to some post explaining how to do it?) + file. (A post explaining how to do it can be found [here](https://insaneinside.net/2017/09/12/whole-crate-bug-reduction-with-creduce.html).) * pnkfelix's [Rust Bug Minimization Patterns] blog post * This post focuses on "heavy bore" techniques, where you are starting with a large, complex cargo project that you wish to