swift

973d04d9 - Revert "Reapply #87697 and fix overload resolution for Sequence+AsyncSequence types. (#88442)" (#88713)

Revert "Reapply #87697 and fix overload resolution for Sequence+AsyncSequence types. (#88442)" (#88713) <!-- The main branch is now in convergence, which means major changes, such as large refactoring or new features, should be avoided. This strategy is intended to maintain the stability of the Swift 6.4 release leading up to the May 4th branch. For any work that requires broad changes or introduces new features, create a feature branch and open a draft pull request. All updates to the swiftlang/swift repository’s main branch require approval from the release managers. A pull request targeting swiftlang/swift will automatically add release managers. You can also contact them via @release-managers in the forum group. --> <!-- Please fill out the following form: --> - **Explanation**: This reverts commit 5ece334724d2543b977acdf991f47c50ebadbafe which aimed to generalize Sequence methods for typed throws and resolve its side effects on overload resolution when a type conforms to both Sequence and AsyncSequence. There appears to be, at least, one more unanticipated side-effect, hence this pre-emptive revert in view of the soon-to-be Swift 6.4 release branching. <!-- A description of the changes. This can be brief, but it should be clear. --> - **Scope**: The said commit is reverted, preserving the recent ~Copyable/consuming alterations to Sequence.reduce(\_:\_:) (#85716). <!-- An assessment of the impact and importance of the changes. For example, can the changes break existing code? --> - **Issues**: Under investigation <!-- References to issues the changes resolve, if any. --> - **Risk**: Low <!-- The (specific) risk to the release for taking the changes. --> - **Testing**: None <!-- The specific testing that has been done or needs to be done to further validate any impact of the changes. --> <!-- Before merging this pull request, you must run the Swift continuous integration tests. For information about triggering CI builds via @swift-ci, see: https://github.com/apple/swift/blob/main/docs/ContinuousIntegration.md#swift-ci Thank you for your contribution to Swift! -->