-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement await
syntax
#60016
Labels
A-async-await
Area: Async & Await
AsyncAwait-Polish
Async-await issues that are part of the "polish" area
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
nikomatsakis
added
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
A-async-await
Area: Async & Await
AsyncAwait-Polish
Async-await issues that are part of the "polish" area
labels
Apr 16, 2019
I've finished this, pending changes to whatever final syntax is chosen. |
CC #51751 |
bors
added a commit
that referenced
this issue
May 7, 2019
Implement built-in await syntax Adds support for .await under the existing async_await feature gate. Moves macro-like await! syntax to the await_macro feature gate. Removes support for `await` as a non-keyword under the `async_await` feature. This new syntax is not final, but is the consensus solution proposed by the lang team, as explained in https://boats.gitlab.io/blog/post/await-decision/ Fix #51719 Fix #51751 Fix #60016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-async-await
Area: Async & Await
AsyncAwait-Polish
Async-await issues that are part of the "polish" area
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
As of this writing, we have not settled the precise syntax we will use for
await
. However, we have decided that we want to decide -- so it makes sense to get started on implementation. This issue is focused purely on implementation issues; the question of what syntax to use is covered in #57640.The text was updated successfully, but these errors were encountered: