From 0a6bc21cb77bd57bf117d2b5ad84c7a449c8337b Mon Sep 17 00:00:00 2001 From: Luca Palmieri <20745048+LukeMathWalker@users.noreply.github.com> Date: Mon, 7 Jul 2025 11:47: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 ab7cc6aa..1d4ee30e 100644 --- a/src/idiomatic/leveraging-the-type-system.md +++ b/src/idiomatic/leveraging-the-type-system.md @@ -33,7 +33,7 @@ Additional items speaker may mention: 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 + doesn't support inheritance, and object decomposition should take into account the constraints introduced by the borrow-checker. - Mention that type-level abstractions are often referred to as "zero-cost