Fix Xcode 16 build failure caused by AsyncSubject #42
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.
Fix AsyncSubject's Failure type conflincting with Apple addition to AsyncSequence starting from Xcode 16 (iOS 18, MacOS 15, Vision OS 2, etc.)
Description
For more information on what caused the issue, see this discussion.
Fixed by:
AsyncSubject
procotol into two protocols:send(element:)
method and dependance toAsyncSequence
and other protocolsFailure
type and thesend(termination:)
methodtypealias
to a conformance of both of these new protocolsThis results in the compiler either:
AsyncSubjectTerminable
's Failure type on its own whenAsyncSequence
doesn't defines it (up until Xcode 16)AsyncSubjectTerminable
andAsyncSequence
's Failure type to be the same type whenAsyncSequence
does define its own Failure type (starting from Xcode 16)Checklist