[6.2][Frontend] Promote AsyncCallerExecution to an upcoming feature
#80982
Conversation
This file contains hidden or 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
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
hborla
approved these changes
Apr 22, 2025
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.
Cherry-pick of #80969
Explanation:
Since SE-0461 has been accepted the experimental feature flag can now be promoted to an upcoming one and renamed to better reflect the semantics of the change.
Main Branch PR: [Frontend] Promote
AsyncCallerExecutionto an upcoming feature #80969Risk: Low (This change should be no-op because no swift interfaces are expected to be using the names yet).
Reviewed By: @hborla
Resolves: rdar://145776322
Testing: Updated existing tests in the test suite.