Skip to content

Commit 8e0bfd4

Browse files
committed
fix bad qualifier
1 parent 43593d0 commit 8e0bfd4

File tree

1 file changed

+3
-3
lines changed
  • content/lessons/05_types_reasoning

1 file changed

+3
-3
lines changed

content/lessons/05_types_reasoning/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -339,15 +339,15 @@ The problem here is that nothing hinders us from implement the trait (with vario
339339

340340
The use of generic types in `Summary` trait makes it semantics like this:
341341

342-
> Any type can be summarized with any type supporting it.
342+
> A type can be summarized with any type supporting it.
343343
344-
When we want the trait to require exactly one possible generic implementation for a given type, we can leverage _associated types_. Example here:
344+
When we want the trait to require exactly one possible generic implementation for a given type, we can leverage *associated types*. Example here:
345345

346346
{{ include_code_sample(path="lessons/05_types_reasoning/trait_associated_type.rs", language="rust") }}
347347

348348
The use of associated types in Summary trait makes it semantics like this:
349349

350-
> Any type can be summarized with at most one specific type.
350+
> A type can be summarized with at most one specific type.
351351
352352
Yet another approach (arguably, the cleanest one) would be to use the `impl trait` syntax in a trait (quite recently stabilized!).
353353
Example:

0 commit comments

Comments
 (0)