dnrops
/
rfcs
mirror of https://github.com/rust-lang/rfcs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify section about associated types being reserved 

We specify that the details about the traits, including the associated
types, are implementation details.  Let's make the section describing
this, with respect to the associated types, more clear and give an
example.

(Thanks to RalfJ and Yosh for raising that this section could be
clarified.)
This commit is contained in:
Travis Cross 2024-07-02 18:24:13 +00:00
parent 6000a0c244
commit a514d3b4ac
1 changed files with 28 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
text/3668-async-closure.md
View File

@ -193,7 +193,34 @@ pub trait AsyncFn<Args>: AsyncFnMut<Args> {
### Associated types of `AsyncFn*` traits are not nameable
Note that, unlike what is true today with the current `Fn*` traits, this RFC reserves as an implementation detail the associates types of the `AsyncFn*` traits, and these will not be nameable as part of the stable interface specified by this RFC.
Unlike what is true today with the current `Fn*` traits, this RFC reserves as an implementation detail the associated types of the `AsyncFn*` traits, and these will not be nameable as part of the stable interface specified by this RFC.
That is, using the existing `FnOnce` trait, we can write this today on stable Rust:
```rust
fn foo<F, T>()
where
F: FnOnce() -> T,
F::Output: Send, //~ OK
{
}
```
(We decided to allow this in [#34365](https://github.com/rust-lang/rust/pull/34365).)
However, this RFC reserves as an implementation detail the associated types of the traits specified above, so this does not work:
```rust
fn foo<F, T>()
where
F: async FnOnce() -> T,
F::Output: Send,
//~^ ERROR use of unstable library feature
F::CallOnceFuture: Send,
//~^ ERROR use of unstable library feature
{
}
```
### `async` bound modifier on `Fn()` trait bounds