[Concurrency] Fix nested await/try parsing and effects checking. #33807
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.
Fix the parsing of await/try/try?/try! so that the two can be nested
(e.g.,
await try f()
ortry await f()
).Then, fix the effects checking logic to preserve all throws-related
information under an
await
, and preserve all async/await-relatedinformation under
try
/try?
/try!
.Add a number of tests, and fix 'await' handling for string
interpolations as well.