Skip to content

Commit 21322a6

Browse files
committed
Delete APIT drawback paragraph
1 parent 7fbc159 commit 21322a6

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

text/0000-impl-trait-type-aliases.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -342,9 +342,6 @@ It is likely that a misunderstanding of the nature of `impl Trait` in argument o
342342

343343
Since we will teach `impl Trait` cohesively (that is, argument-position, return-position and type alias `impl Trait` at the same time), it is unlikely that users who understand `impl Trait` will be confused about aliases. (What's more, examples in the reference will illustrate this clearly.)
344344

345-
## Argument-position `impl Trait`
346-
As described in the [Guide-level explanation](#guide-level-explanation), although we can freely replace an occurence of a return-position `impl Trait` with an `impl Trait` type alias, we cannot freely replace an occurrence of an argument-position `impl Trait`, as argument-position `impl Trait` may be polymorphic, determined by the caller as with a generic parameter. However, `impl Trait` type aliases are strictly monomorphic. Unfortunately this is an inherent restriction due to the inconsistency of argument-position `impl Trait` with return-position `impl Trait` (regarding the quantifier scope).
347-
348345
# Rationale and alternatives
349346
[rationale-and-alternatives]: #rationale-and-alternatives
350347
The justification for the type alias syntax proposed here comes down to two key motvations:

0 commit comments

Comments
 (0)