Skip to content

Commit c21da6c

Browse files
authored
Merge pull request #2488 from rust-lang/Centril-patch-1
RFC 2071: Fix typo, existentail -> existential
2 parents 74d4623 + 9664b54 commit c21da6c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

text/2071-impl-trait-type-alias.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -371,7 +371,7 @@ trait Foo<T> {
371371
}
372372

373373
impl<T> Foo<T> for MyStruct {
374-
existentail type Bar: Trait;
374+
existential type Bar: Trait;
375375
fn bar() -> Self::Bar {
376376
...
377377
// Returns some type MyBar<T>
@@ -496,7 +496,7 @@ should be "no" since doing so would give away the underlying type being
496496
hidden beneath the impl. Still, some version of this feature could be
497497
used eventually to implement traits or functions for closures, or
498498
to express conditional bounds in existential type signatures
499-
(e.g. `existentail type Foo<T> = impl Debug; impl<T: Clone> Clone for Foo<T> { ... }`).
499+
(e.g. `existential type Foo<T> = impl Debug; impl<T: Clone> Clone for Foo<T> { ... }`).
500500
This is a complicated design space which has not yet been explored fully
501501
enough. In the future, such a feature could be added backwards-compatibly.
502502

@@ -543,7 +543,7 @@ considered:
543543
- We could omit a keyword altogether and use `type Foo: Trait;` syntax
544544
(outside of trait definitions).
545545

546-
A more divergent alternative is not to have an "existentail type" feature at all,
546+
A more divergent alternative is not to have an "existential type" feature at all,
547547
but instead just have `impl Trait` be allowed in type alias position.
548548
Everything written `existential type $NAME: $BOUND;` in this RFC would instead be
549549
written `type $NAME = impl $BOUND;`.

0 commit comments

Comments
 (0)