Bill Phillips

That's a great example. @JakeWharton, I don't think we can fix this as long as we are heavily buffering the internal channel; we'd need to switch it to `RENDEZVOUS`.

This has also hit us pretty hard at Cash. We're raising the issue with upstream.

```kotlin @Composable fun debounce(value: T, duration: Duration): T { // ???? } ``` This can't be implemented on a `StateFlow`, but it should be implementable in compose

> I think that perhaps we want to consider accepting a frame clock even when using immediate mode. I would think this would be equivalent to using the frame clock...

My only concern with a function like that is that it can hide legitimate test issues: by skipping items that are not of interest, we also prevent failures that may...

I think I'd like to put my opinion down as against this PR as written for the following reasons: * It's more intrusive than it needs to be: at its...

> That's the good part about this change - the value of the molecule should not change when the stateflow gets rebooted. The entire composition remains active, including the state...

If this state is intended to be consumed within the Molecule, would it be more idiomatic to expose it as a `State` rather than as a `StateFlow`? Finally, if the...

> but it will always restart the launched effect when the composition flips from inactive to active, whereas this variant allows you to eg. only restart parts of your coroutine,...

I love the idea of including list literals, but the whole question of what to do about custom types, mutable collections, etc... it dramatically complicates the feature and dramatically complicates...