Update the comment and bug ID explaining why a workaround in ConfirmationTests is still needed #1391
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
…tionTests is still needed
stmontgomery
requested review from
briancroom,
jerryjrchen and
suzannaratcliff
as code owners
stmontgomery
added
documentation
grynspan
reviewed
Nov 4, 2025
| /// argument type for `confirmedOutOfRange(_:)`. Although we can now write | ||
| /// `any RangeExpression<Int> & Sequence<Int> & Sendable` as of Swift 6.2 | ||
| /// (per [swiftlang/swift#76705](https://github.com/swiftlang/swift/pull/76705)), | ||
| /// attempting to form an array of such values crashes at runtime. ([163980446](rdar://163980446)) |
grynspan
added
the
workaround
jerryjrchen
approved these changes
Nov 4, 2025
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.
This has no functional change, it just updates the comment and tracking bug ID explaining why a certain workaround in
ConfirmationTests.swiftfor existential composition of parameterized protocol types is still necessary.Motivation:
I tried removing this workaround recently, since it should no longer be necessary, but discovered that while the syntax is now valid in Swift 6.2, there's a new blocker—the runtime crash tracked by the new bug ID. It's helpful to document this so we know why the workaround is still needed.
Note that even if/when this remaining issue is resolved, this capability will require a certain minimum OS version on Apple platforms, since the compiler fix had a runtime component.
Checklist: