Skip to content

Conversation

@rjmccall
Copy link
Contributor

This is the test case from #69028 (comment).

expansion component.

Use this in emitPackTransform; this reorders a couple of projections,
but that's fine, and the result is much cleaner and has better separation
of concerns.
This only happens when binding parameters under an abstraction pattern
and can therefore only currently happen with closures passed to functions
that take variadic generic tuples (that happen to vanish).

This is relatively straightforward using ExpandedTupleInputGenerator,
and it cleans the code up a fair bit.
@rjmccall
Copy link
Contributor Author

@swift-ci Please test

@slavapestov
Copy link
Contributor

Thanks!

@alex-reilly-dd
Copy link

Thanks!

@rjmccall rjmccall merged commit cef53c6 into swiftlang:main Dec 16, 2025
5 checks passed
@rjmccall rjmccall deleted the vanishing-tuple-param-binding branch December 16, 2025 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants