From a44eaa90950c6ee5ea4cc7d6fad1b3e9b972cea2 Mon Sep 17 00:00:00 2001 From: Luca Palmieri <20745048+LukeMathWalker@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:46:33 +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 7ad22e94..ffca9fc0 100644 --- a/src/idiomatic/leveraging-the-type-system.md +++ b/src/idiomatic/leveraging-the-type-system.md @@ -27,7 +27,7 @@ Additional items speaker may mention: topic, with examples written in F#. - Despite Rust's functional roots, functional design patterns don't translate as-is - to Rust. For instance, extensive use of higher-kinded functions and types can + 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.