You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to have an async Operation subclass that wraps a computation and has an associated Promise. This would make it easier to integrate promises into dependency management that Operation is good at expressing.
With this approach, the client would create an instance of the Operation subclass, and the instance would have an associated read-only promise property that returns a promise that is resolved by the operation's computation. No computation occurs until the operation starts (either by calling start() or by adding it to a queue). Requesting cancellation of the promise should call cancel() on the operation, and calling cancel() on the operation should request cancellation of the promise.
The text was updated successfully, but these errors were encountered:
This is an `Operation` subclass that wraps a `Promise`, including
deferred execution of the handler that resolves the promise.
This is just the Swift support. The Obj-C support will come in a
separate commit.
Fixes#58.
This is an `Operation` subclass that wraps a `Promise`, including
deferred execution of the handler that resolves the promise.
This is just the Swift support. The Obj-C support will come in a
separate commit.
Fixes#58.
This is an `Operation` subclass that wraps a `Promise`, including
deferred execution of the handler that resolves the promise.
This is just the Swift support. The Obj-C support will come in a
separate commit.
Fixes#58.
This is an `Operation` subclass that wraps a `Promise`, including
deferred execution of the handler that resolves the promise.
This is just the Swift support. The Obj-C support will come in a
separate commit.
Fixes#58.
It would be useful to have an async
Operation
subclass that wraps a computation and has an associatedPromise
. This would make it easier to integrate promises into dependency management thatOperation
is good at expressing.With this approach, the client would create an instance of the
Operation
subclass, and the instance would have an associated read-onlypromise
property that returns a promise that is resolved by the operation's computation. No computation occurs until the operation starts (either by callingstart()
or by adding it to a queue). Requesting cancellation of the promise should callcancel()
on the operation, and callingcancel()
on the operation should request cancellation of the promise.The text was updated successfully, but these errors were encountered: