-
Notifications
You must be signed in to change notification settings - Fork 88
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e2b7ace
commit 680f40e
Showing
2 changed files
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Glossary | ||
|
||
If you follow discussions in the async ecosystem you're likely to find acronyms being tossed around, many of which refer to language features that are in-progress. | ||
What follows is a best-effort list of those acronyms and links to resources discussing the language features. | ||
|
||
## AFIT - async fn in trait | ||
- [RFC #3185](https://github.com/rust-lang/rfcs/pull/3185) | ||
- Allows static dispatch of `async fn`s in traits | ||
|
||
## RPITIT - return position `impl trait` in traits | ||
- [RFC #3425](https://github.com/rust-lang/rfcs/pull/3425) | ||
- Allows `impl trait` as a return type in trait definitions | ||
|
||
## RTN - return type notation | ||
- [Tracking Issue: rust#109417](https://github.com/rust-lang/rust/issues/109417) | ||
- Experimental, pre-RFC feature providing bounds for return types on `async fn`s |