From 28d83e5888896cfd44d89785da76fe308976d1f1 Mon Sep 17 00:00:00 2001 From: Luca Palmieri <20745048+LukeMathWalker@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:46:01 +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 5da0e62b..7ad22e94 100644 --- a/src/idiomatic/leveraging-the-type-system.md +++ b/src/idiomatic/leveraging-the-type-system.md @@ -26,7 +26,7 @@ Additional items speaker may mention: types. ["Domain Modeling Made Functional"][1] is a great resource on the topic, with examples written in F#. -- Despite its functional roots, functional design patterns don't translate as-is +- 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 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