Skip to content

Commit 0e86f55

Browse files
Update text/0000-return-type-notation.md
Co-authored-by: Tyler Mandry <tmandry@gmail.com>
1 parent a9de455 commit 0e86f55

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/0000-return-type-notation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -959,7 +959,7 @@ Unlike a regular associated type, this RFC does not allow a trait bound that spe
959959
rpjohnst suggested that we may wish to support a syntax like `T: Trait<method(..) -> T>`, perhaps in conjunction with specified argument types.
960960
They further pointed out that permitting `T::method(..)` as a standalone type could be seen as inconsistent, given that `fn foo()` is normally shorthand for `-> ()`.
961961
However, *not* supporting `T::method(..)` as a standalone type could also be seen as inconsistent, since normally `T: Trait<Bar: Send>` and `T::Bar: Send` are equivalent.
962-
Prior to stabilizing the "send position" syntax, we should be sure we are comfortable with this.
962+
Prior to stabilizing the "associated type position" syntax, we should be sure we are comfortable with this.
963963

964964

965965
# Future possibilities

0 commit comments

Comments
 (0)