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
UnconfinedTestDispatcher didn't get the stable treatment in #3622. This is a tracking issue for its stabilization at some point in the future.
For us, this is the final remaining unstable API preventing Turbine from going 1.0. Turbine collects flows in a coroutine which was traditionally launched on the UNCONFINED dispatcher. This is to ensure we do not miss any emitted values from a flow when it performs some operation on backpressure (conflating, dropping, etc.). With the new runTest infrastructure, we were forced to take on a 'kotlinx-coroutines-test' dependency in order to conditionally use UnconfinedTestDispatcher wrapped around the caller's TestCoroutineScheduler so as to not break virtual time.
The text was updated successfully, but these errors were encountered:
UnconfinedTestDispatcher
didn't get the stable treatment in #3622. This is a tracking issue for its stabilization at some point in the future.For us, this is the final remaining unstable API preventing Turbine from going 1.0. Turbine collects flows in a coroutine which was traditionally launched on the
UNCONFINED
dispatcher. This is to ensure we do not miss any emitted values from a flow when it performs some operation on backpressure (conflating, dropping, etc.). With the newrunTest
infrastructure, we were forced to take on a 'kotlinx-coroutines-test' dependency in order to conditionally useUnconfinedTestDispatcher
wrapped around the caller'sTestCoroutineScheduler
so as to not break virtual time.The text was updated successfully, but these errors were encountered: