Disfavor overloads of __checkFunctionCall() with variadic generics.
#1389
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
This works around rdar://122011759 which appears to have been exacerbated by swiftlang/swift#84907.
grynspan
requested review from
briancroom,
jerryjrchen,
stmontgomery and
suzannaratcliff
as code owners
grynspan
added
workaround
stmontgomery
approved these changes
Nov 3, 2025
grynspan
added a commit
that referenced
this pull request
Nov 7, 2025
…#1389) This works around rdar://122011759 which appears to have been exacerbated by swiftlang/swift#84907. For example: ```swift let file = try #require(fmemopen(nil, 1, "wb+")) ``` The third parameter of `fmemopen()` is of type `const char *` (AKA `UnsafePointer<CChar>`) and we're passing the string literal `"wb+"` which is implicitly cast to a C string by the compiler. However, overload resolution of the expansion function used by `#require()` is now preferring an overload that uses variadic generics, and that overload is impacted by a compiler issue (rdar://122011759) that causes it to pass a garbage pointer as the temporary C string. Previously, the type checker would pick an overload with a concrete, finite set of generic arguments (`<T, Arg0, Arg1, Arg2, R>` instead of `<T, each U, R>`.) ### Checklist: - [x] Code and documentation should follow the style of the [Style Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md). - [x] If public symbols are renamed or modified, DocC references should be updated.
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.
This works around rdar://122011759 which appears to have been exacerbated by swiftlang/swift#84907.
For example:
The third parameter of
fmemopen()is of typeconst char *(AKAUnsafePointer<CChar>) and we're passing the string literal"wb+"which is implicitly cast to a C string by the compiler. However, overload resolution of the expansion function used by#require()is now preferring an overload that uses variadic generics, and that overload is impacted by a compiler issue (rdar://122011759) that causes it to pass a garbage pointer as the temporary C string. Previously, the type checker would pick an overload with a concrete, finite set of generic arguments (<T, Arg0, Arg1, Arg2, R>instead of<T, each U, R>.)Checklist: