SE-0492: Allow any @convention(c) function conversions #86088
+10
−1
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
Contributor
Author
|
@swift-ci please test |
DougGregor
approved these changes
Dec 16, 2025
DougGregor
approved these changes
Dec 16, 2025
4045951 to
2d6ed72
Compare
Contributor
Author
|
@swift-ci please test |
Contributor
|
@swift-ci test Windows |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Bugfix for
@sectionsupport. See the attached testcase, where we currently reject the closure because the AST representation does represent "f" as a capture. But for any legal@convention(c)function conversion, we don't need to impose any requirements on the closure, because we are guaranteed that it'll be a single function pointer after lowering.