Skip to content

Conversation

DougGregor
Copy link
Member

Fix the parsing of await/try/try?/try! so that the two can be nested
(e.g., await try f() or try await f()).

Then, fix the effects checking logic to preserve all throws-related
information under an await, and preserve all async/await-related
information under try/try?/try!.

Add a number of tests, and fix 'await' handling for string
interpolations as well.

Fix the parsing of await/try/try?/try! so that the two can be nested
(e.g., `await try f()` or `try await f()`).

Then, fix the effects checking logic to preserve all throws-related
information under an `await`, and preserve all async/await-related
information under `try`/`try?`/`try!`.

Add a number of tests, and fix 'await' handling for string
interpolations as well.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@DougGregor DougGregor merged commit 11154b1 into swiftlang:master Sep 5, 2020
@DougGregor DougGregor deleted the concurrency-nested-await-try branch September 5, 2020 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant