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

Add open question around resolution of #112194

This commit is contained in:
Tyler Mandry 2023-06-02 15:42:22 -07:00
parent caf455a1f0
commit 6adfb20ae7
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
text/0000-return-position-impl-trait-in-traits.md
View File

@ -646,6 +646,7 @@ There are a number of crates that do desugaring like this manually or with proce
[unresolved-questions]: #unresolved-questions [unresolved-questions]: #unresolved-questions
- Should we stabilize this feature together with `async fn` to mitigate hazards of writing a trait that is not forwards-compatible with its desugaring? (See [drawbacks].) - Should we stabilize this feature together with `async fn` to mitigate hazards of writing a trait that is not forwards-compatible with its desugaring? (See [drawbacks].)
- Resolution of [#112194: RPITIT is allowed to name any in-scope lifetime parameter, unlike inherent RPIT methods](https://github.com/rust-lang/rust/issues/112194)
# Future possibilities # Future possibilities
[future-possibilities]: #future-possibilities [future-possibilities]: #future-possibilities