[CSRanking] Adjust ranking of makeIterator
overloads in for-in
context
#61075
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.
Prefer an overload of
makeIterator
that satisfiesSequence#makeIterator
requirement when.makeIterator()
is implicitly injected after sequence expression in
for-in
loop context.
This helps to avoid issues related to conditional conformances
to
Sequence
that addmakeIterator
preferred by overloadingrules that could change behavior i.e.:
makeIterator
declared in theArray
extension is not a witness toSequence#makeIterator
and shouldn't be used because that would change runtime behavior.Resolves: #60514
Resolves: #60958