Make AsyncPredicate Sendable, constrain it to Sendable types #1072
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.
As part of concurrency checking,
AsyncPredicate
needs to be Sendable. Part of that is that the closure needs to be Sendable andAsyncPredicate
needs to be constrained to only Sendable types.As part of interop with
AsyncPredicate
,Predicate
needs to be Sendable. Though, it's ok to only makePredicate
Sendable when the type it works with isSendable
(that is, we have:extension Predicate: Sendable where T: Sendable {}
).This also fixes compiler errors in Nimble associated with making the closures passed to Predicate Sendable.