Turbine question: what's the difference between `e...

# coroutines

[Sam]

Turbine question: what's the difference between expectNoEvents() and ensureAllEventsConsumed()?

[Sam]

From the API doc:

• `expectNoEvents()`: Assert that there are no unconsumed events which have already been received.

• `ensureAllEventsConsumed()`: Assert that all events that have occurred so far on this ReceiveTurbine have been consumed.

That sounds like the same words in a different order, unless I'm missing something

[kevin.cianfarini]

Sorry, but I don't see ensureAllEventsConsumed listed here? https://cashapp.github.io/turbine/docs/1.x/-turbine/app.cash.turbine/index.html

[kevin.cianfarini]

Which version are you using?

[Sam]

I'm on 1.2.0. Here's some links:
• https://cashapp.github.io/turbine/docs/1.x/-turbine/app.cash.turbine/-receive-turbine/expect-no-events.html
• https://cashapp.github.io/turbine/docs/1.x/-turbine/app.cash.turbine/-receive-turbine/ensure-all-events-consumed.html

[Sam]

(They're member functions, not extensions, so they don't show up in the navigation sidebar)

[kevin.cianfarini]

They definitely seem slightly different but the docs are very similar. I'm not sure. Maybe cross post into #C5HT9AL7Q?

[Sam]

Thanks, didn't know about that channel 👍

[Robert Williams]

Looking at the code I only see two very subtle differences:
• ensureAllEventsConsumed respects cancelAndIgnoreRemainingEvents to treat ignored events as consumed
• ensureAllEventsConsumed includes all events in the failure message whereas expectNoEvents only includes the first. This might be useful or noisy depending on how many events you have

[Robert Williams]

Also of interest is that prior to this refactor, ensureAllEventsConsumed was an internal API, not part of the public interface. It's not entirely obvious whether this change was intentional

[Sam]

Thanks! @jw do you have any more insight?

[jw]

Not off the top of my head. You can file an issue and I can look when I have time, or maybe Bill will