From 38e6dbda2b34803e3c542230096d73079a72271c Mon Sep 17 00:00:00 2001 From: Luca Palmieri <20745048+LukeMathWalker@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:46:49 +0200 Subject: [PATCH] Apply suggestion from @gribozavr Co-authored-by: Dmitri Gribenko --- src/idiomatic/leveraging-the-type-system.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/idiomatic/leveraging-the-type-system.md b/src/idiomatic/leveraging-the-type-system.md index ffca9fc0..ab7cc6aa 100644 --- a/src/idiomatic/leveraging-the-type-system.md +++ b/src/idiomatic/leveraging-the-type-system.md @@ -30,7 +30,7 @@ Additional items speaker may mention: to Rust. For instance, extensive use of higher-order functions and higher-kinded types can result in code that is harder to read and maintain. Design patterns in Rust must take into account (and leverage!) the granular control over mutability - that comes with its borrow-checker. + that comes with its borrow checker. - The same caution should be applied to object-oriented design patterns. Rust doesn't support inheritance, and object boundaries must be mindful of the