Timeout Handler #4
Merged
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.
Adds an overload that includes a
Timeout
object that can be used to extend, move or cancel the timeout.For example, the timeout can be extended by 1 second for every iteration of a sequence;
If possible
Timeout
will be marked~Escapable
in Swift 6.2, but for now a runtime assertion occurs if the object escapes the closure (via a canary and withoutActuallyEscaping)Variants
Timeout
is shared across concurrency domains — the isolation of thebody
closure doing the work and theTask
performing and processing the timeout. Therefore, a flag is returned indicating if the timeout was in fact extended or if the timeout had already expired (and was unwinding);let didExtend = timeout.expire(seconds: 1.0)
A deadline can also be used:
let didExtend = timeout.expire(after: .now + .seconds(1.0))
The timeout can also be cancelled indefinitely:
let didCancel = timeout.cancelExpiration()
Or expired immediately preventing any more extensions:
let didExpire = timeout.expireImmediatley()