If JavaFx dispatcher is present in the classpath, using any other dispatcher will start the JavaFx platform.

[jcornaz]

Hello,

Please consider the following code:

suspend fun main() {
  withContext(Dispatchers.IO) {}
  println("done")
}

This code has the following output:

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by kotlinx.coroutines.javafx.JavaFxDispatcherKt (file:~/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-javafx/0.30.1-eap13/6eec25d3a9961d45fd2c097b0e038d348b3cc243/kotlinx-coroutines-javafx-0.30.1-eap13.jar) to method com.sun.javafx.application.PlatformImpl.startup(java.lang.Runnable)
WARNING: Please consider reporting this to the maintainers of kotlinx.coroutines.javafx.JavaFxDispatcherKt
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
done

Here I'm not talking about the warning which is already addressed in #463.

No, here the concern is the fact that the JavaFx platform has been started. And since the JavaFx platform thread is a user-thread, it prevents the program to terminate.

This behavior only happens if kotlinx-coroutines-javafx is in the classpath.

[qwwdfsad]

We should instantiate DIspatchers.Main lazily