Add async / await
#77
Merged
Conversation
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
Allows async in function declarations and type signatures. `async` must always come before `throws`. This keyword also has to go in the semi suppressor for the same reason `throws` and `rethrows` are there. Also allows `await` before any expression. Gives it the same special behavior that `try` gets, where it has an affinity for function calls and ternary operators, but can be placed before any expression. Special cases the `for try await` syntax that Swift added for async sequences. That doesn't appear to have made it into the grammar yet. Usage makes it seem like it must be either `for await` or `for try await`, not permiting just `for try` alone, but without an official reference it seems best to simply allow `for try`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows async in function declarations and type signatures.
asyncmustalways come before
throws. This keyword also has to go in the semisuppressor for the same reason
throwsandrethrowsare there.Also allows
awaitbefore any expression. Gives it the same specialbehavior that
trygets, where it has an affinity for function callsand ternary operators, but can be placed before any expression.
Special cases the
for try awaitsyntax that Swift added for asyncsequences. That doesn't appear to have made it into the grammar yet.
Usage makes it seem like it must be either
for awaitorfor try await, not permiting justfor tryalone, but without anofficial reference it seems best to simply allow
for try.