SIL: Lower closure functions' captures in their own expansion context. #39624
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
The capture arguments are a private contract between the closure and its context, and will only ever be bound from the enclosing context, so there's no need to obscure opaque underlying types (unless it's serializable because it's in inlinable code, in which case we continue to use the minimal type expansion context to account for inlining as before.) Fixes rdar://83378116.
|
@swift-ci Please test |
|
@swift-ci Please test source compatibility |
1 similar comment
|
@swift-ci Please test source compatibility |
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.
The capture arguments are a private contract between the closure and its
context, and will only ever be bound from the enclosing context, so
there's no need to obscure opaque underlying types (unless it's
serializable because it's in inlinable code, in which case we
continue to use the minimal type expansion context to account for
inlining as before.)
Fixes rdar://83378116.