Async scheduled work creates implicit child state machines, almost always must be reified so we can see/affect interactions with parent.
Conversation
Replying to
did you read my post from yesterday or is this a great coincidence?
2
No, but I will now.
Replying to
@jarjar2k7 Lazy streams are perilous, I believe; you often need arrow-level control to specify *when* work will happen.
Replying to
@jarjar2k7 Even if there are no side-effects, you may want to control execution timing if computation is expensive.
Replying to
Ran into this even just this morning (I think) with authentication calls.
Replying to
So is that a reason to use NSOperation only, or to define a custom state machine to use with every dispatch_async call?
1
Depends on your needs, I think, but operations are a decent abstraction. Signals, too.
1
Replying to
Does this mean you implicitly dislike C#’s async/await?
1
1
Depends on how it's used. You can get a Task out of an async fn, so it can be used in a confined way.