Zach Klippenstein

I _think_ this might be related to issue #3253, since this bug doesn't happen if the wrapping interceptor returns the incoming `Continuation` (not a `DispatchedContinuation`) directly instead of delegating to...

I have a different use case for this. I have a coroutine that runs a loop to process a UI framework (calculate an initial state, wait for events, calculate new...

That would be the default behavior if `WorkflowLayout` were compose (since it would presumably `collectAsState` or `collectAsStateWithLifecycle`). I think for a `View` we could do something like this: ```kotlin suspend...

> We're not an animation tool. If we were, we'd still want to only operate on frames 😂

Actually I think we should probably just make `show` debounce itself until frame boundary, not put the logic in `take`. 

I haven't thought about nesting. If `show` is called as a result of a parent `WorkflowLayout` propagating the renderings down the view tree, then it shouldn't defer ever. (Compose also...

> In fact, CONFLATE_STALE_RENDERINGS is basically a no-op when using the AndroidUiDispatcher.Main to dispatch the runtime and consume the renderings. > … > On Android context where we use this...

I think there's a slight difference in behavior with this implementation vs the one in #1315, which is that the latter will still start collecting both flows eagerly but it...

All Flow operators are multi-platform by default.

What does `imageLoader.execute` actually do asynchronously in the fast path (memory cache hit)? One idea: use a custom dispatcher, similar to the one Compose uses, that drains the queue right...