This replaces the Dispatch-based version of async toEventually with one that uses native Swift Concurrency components This was done to eliminate the chance that the matcher could be polled more than one at a time, and to also make way for future Sendable requirements.
This is a drop-in replacement for the Dispatch-Based approach to the async variant.
The PR should summarize what was changed and why. Here are some questions to
help you if you're not sure:
What behavior was changed?
What code was refactored / updated to support this change?
What issues are related to this PR? Or why was this change introduced?
Checklist - While not every PR needs it, new features should consider this list:
[x] Does this have tests?
[x] Does this have documentation?
[ ] Does this break the public API (Requires major version bump)?
[x] Is this a new feature (Requires minor version bump)?
This replaces the Dispatch-based version of async toEventually with one that uses native Swift Concurrency components This was done to eliminate the chance that the matcher could be polled more than one at a time, and to also make way for future Sendable requirements.
This is a drop-in replacement for the Dispatch-Based approach to the async variant.
The PR should summarize what was changed and why. Here are some questions to help you if you're not sure:
Checklist - While not every PR needs it, new features should consider this list: