if you use ` launch` or ` async` use the `Dispatchers Unconf kotlinlang #coroutines

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

zak.taccardi

11/12/2018, 4:46 PM

if you use

.launch

.async

, use the

Dispatchers.Unconfined

which should help the coroutine finish before your test does

👌 1

gildor

11/12/2018, 11:07 PM

Unconfined now uses event loop, so it's not completely syncronous even when running on the same thread

zak.taccardi

11/12/2018, 11:53 PM

In JS?

gildor

11/13/2018, 12:44 AM

I believe on every platform

And definitely on JVM

https://github.com/Kotlin/kotlinx.coroutines/issues/704

👍 1

zak.taccardi

11/13/2018, 12:48 AM

Yikes. This looks like something that could potentially break all my tests

And we're on Kotlin 1.2 pre-stable co-routines. And that change isn't available until

1.0.0-rc1

which requires 1.3

Should be fun!

gildor

11/13/2018, 12:50 AM

I had problem in tests, but it was related that I used runBlocking with wrong Unconfined context.

But in general everything worked after migration

https://github.com/gildor/kotlin-coroutines-retrofit/commit/41473bf38ffacd35b9764e1219576582b7c47712

3 Views

#coroutines Join Slack