Jake Wharton

> There seems to have been a bad interaction with runTest in the past where using virtual time timeout would cause Turbine to hang, but that issue no longer appears...

This test verifies the timeout behavior: https://github.com/cashapp/turbine/blob/fce249a6f78e97fa9a9486e08ad013c6b83d224d/src/commonTest/kotlin/app/cash/turbine/FlowTest.kt#L617-L629

I do not believe we need that option, no. The existing timeout not running on wall clock time is just a bug that needs fixed. Someone will get to it...

I have never used LiveData. Can you provide a self-contained failing test case?

I do not like the idea of an assertions lambda. Conflating exception usage for logic and test failure within a single test function is not something that I think is...

Turbine uses an unconfined collector which runs concurrently with your test lambda to ensure that we see all values. We do not have a mechanism for applying backpressure to the...

We can possibly design a variation of the API that allows applying backpressure by using a channel with a smaller buffer and potentially an intermediate coroutine which controls the number...

Okay my thought here is that we basically let you control the number of buffered items by blocking the collector. By default it's infinite (the current behavior). You can explicitly...

I think it would be the same API. You would call `.test(initialCapacity = 1) { .. }` (or whatever you want) which would allow at most 1 item into the...

I mean we can omit it and start with only two modes: rendezvous or unlimited buffer. If someone complains at least we have an idea on how to build support...