Append subsection to SF-0036 with explanation of preference for BidirectionalCollection over Sequence#1994
Open
MatthewTurk247 wants to merge 1 commit into
Conversation
Contributor
|
@swift-ci please test |
itingliu
approved these changes
May 26, 2026
Contributor
|
Actually can you rebase this and retarget this onto the 6.4 branch so it's clear that this is part of that change? |
…ectionalCollection over Sequence
MatthewTurk247
force-pushed
the
proposal/initializers-join-predicates-subsection-sequence
branch
from
a649697 to
dbe03c1
Compare
Contributor
|
@swift-ci please test |
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
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 pull request adds a subsection explaining why
Predicate(all:)andPredicate(any:)expectBidirectionalCollectiontypes rather than the broader set ofSequencetypes.