A modern programming language that makes developers happier.

kotlinlang

Anyone know if it is safe for an app (Android app specifically) that is still on Coroutines `1.5.2` to use a 3rd party library that is built with Coroutines `1.6.0`. I see in the <https://github.com/Kotlin/kotlinx.coroutines/releases/tag/1.6.0|changelog> that there are some breaking changes which is why I ask.

I’m working on it. But that `kotlinx-coroutines-test:1.6.0` migration is quite the effort :sweat_smile:. It’s a large codebase with a lot of tests that now fail with the new version even if we continue using the deprecated ~`runBlockingTest`~. So I’m trying to decide if we should halt on including this 3rd party library until we finally migrate our app to Coroutines `1.6.0`.

Most likely my team and I will just wait until we complete the migration to `1.6.0`.

We are on 1.5.2 because of <https://github.com/Kotlin/kotlinx.coroutines/issues/3136>

So far, the test migration effort has significantly less friction if I use `UnconfinedTestDispatcher`. This will at least get me to update to `1.6.0` sooner. Once that is done, then there can be a follow-up effort of switching to `StandardTestDispatcher`. But that alone is looking like a massive effort.