Adapt to Tuple-In-OptionalSome Patterns in Space Projection #31714
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 test |
|
@swift-ci test source compatibility |
|
Build failed |
The space engine goes out of its way to rewrite OptionalSome patterns using the postfix-? sugar into .some(...). Unfortunately, it performed the following remapping: (x, y, z, ...)? -> .some(x, y, z, ...) This syntactic form used to behave correctly. However, we are no longer flattening nested tuples so the correct rewrite is: (x, y, z, ...)? -> .some((x, y, z)) Correct this space projection rule. rdar://62200966
|
@swift-ci smoke test |
|
⛵ |
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 space engine goes out of its way to rewrite OptionalSome patterns
using the postfix-? sugar into .some(...). Unfortunately, it performed
the following remapping:
This syntactic form used to behave correctly. However, we are no longer
flattening nested tuples so the correct rewrite is:
Correct this space projection rule.
rdar://62200966