@@ -371,7 +371,7 @@ trait Foo<T> {
371
371
}
372
372
373
373
impl <T > Foo <T > for MyStruct {
374
- existentail type Bar : Trait ;
374
+ existential type Bar : Trait ;
375
375
fn bar () -> Self :: Bar {
376
376
...
377
377
// Returns some type MyBar<T>
@@ -496,7 +496,7 @@ should be "no" since doing so would give away the underlying type being
496
496
hidden beneath the impl. Still, some version of this feature could be
497
497
used eventually to implement traits or functions for closures, or
498
498
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> { ... }` ).
500
500
This is a complicated design space which has not yet been explored fully
501
501
enough. In the future, such a feature could be added backwards-compatibly.
502
502
@@ -543,7 +543,7 @@ considered:
543
543
- We could omit a keyword altogether and use ` type Foo: Trait; ` syntax
544
544
(outside of trait definitions).
545
545
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,
547
547
but instead just have ` impl Trait ` be allowed in type alias position.
548
548
Everything written ` existential type $NAME: $BOUND; ` in this RFC would instead be
549
549
written ` type $NAME = impl $BOUND; ` .
0 commit comments