Skip to content
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

Closed
nikomatsakis opened this issue Apr 16, 2019 · 3 comments
Closed

Implement await syntax #60016

nikomatsakis opened this issue Apr 16, 2019 · 3 comments

Comments

@nikomatsakis
Copy link
Contributor

@nikomatsakis nikomatsakis commented Apr 16, 2019

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.

@cramertj
Copy link
Member

@cramertj cramertj commented Apr 23, 2019

I've finished this, pending changes to whatever final syntax is chosen.

@estebank
Copy link
Contributor

@estebank estebank commented Apr 25, 2019

CC #51751

@cramertj
Copy link
Member

@cramertj cramertj commented Apr 25, 2019

@estebank Yeah, it fixes #51751 and #51719.

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
@bors bors closed this in #60586 May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants