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

Should async/await be strict keywords? #64853

Closed
ehuss opened this issue Sep 27, 2019 · 2 comments · Fixed by #64875
Closed

Should async/await be strict keywords? #64853

ehuss opened this issue Sep 27, 2019 · 2 comments · Fixed by #64875

Comments

@ehuss
Copy link
Contributor

@ehuss ehuss commented Sep 27, 2019

My impression is that async and await should be strict keywords. They are currently marked as "unused" or "reserved" (unused, unstable). I think the main consequence is that in error messages it is called a reserved keyword if you try to use it as an identifier, when it should just say "keyword".

@petrochenkov
Copy link
Contributor

@petrochenkov petrochenkov commented Sep 28, 2019

Keywords are supposed to migrate from the "reserved-unused" category to "used" immediately after or together with their stabilization. (There are some related comments on the keyword lists in symbol.rs).
Stable async/await is already on beta, right? Then it's time to mark the keywords as "used" as well.

@ehuss
Copy link
Contributor Author

@ehuss ehuss commented Sep 28, 2019

Thanks, I'll take a look at updating it.

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