[CSApply] NFC: Clean up some duplicated logic for propagating async
from contextual types to closure types.
#37282
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.
This is a follow-up to #37263, where I accidentally duplicated some code in
coerceToType
. The new code is clearer about whenasync
is propagated to closure types, which is when the effect is not polymorphic or when the closure inherits the surrounding actor context.Note that this change preserves the behavior that
async
is propagated to closures that inherit the surrounding actor context, even if the closure is an argument to areasync
function. I'm not actually sure how@_inheritActorContext
andreasync
are supposed to interact.