K/N Dispatchers.IO import conflicts

[matejdro]

Describe the bug

It seems there is an import conflict regarding Dispatchers.IO on the K/N vs JVM.

Following code compiles on the JVM:

import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.withContext

suspend fun test() {
    withContext(Dispatchers.IO) {
        
    }
}

But it fails on the K/N:

Cannot access 'val IO: CoroutineDispatcher': it is internal in 'kotlinx.coroutines.Dispatchers'.

the solution is to add the import manually:

import kotlinx.coroutines.IO

however, when performing "Optimize imports" actions in the KMP common code, IntelliJ will remove that import, causing the K/N builds to fail afterwards, without IDE showing anything red.

This makes it difficult to work in the common code with automatic import optimizations enabled as IntelliJ will keep removing this.

Is this a bug in the IntelliJ or the coroutines library?

[dkhalanskyjb]

It's an IDE bug. In my view, any scenario where the IDE automatically transforms correct code into incorrect code is one. The IDE issue tracker is here: https://youtrack.jetbrains.com/.

On a separate note, kotlinx.coroutines should also expose internal val IO in Kotlin/Native Dispatchers as public the same way as JVM does, though. Not because we want to work around the IDE bug, but just because it's inconvenient and inconsistent to add IO as an extra import in Native-only source sets.

[matejdro]

In my view, any scenario where the IDE automatically transforms correct code into incorrect code is one

However, can the IDE be aware that specifically K/N library is different, when common library exposes the IO as a public variable?

[dkhalanskyjb]

Yes, certainly, the IDE sees everything the compiler sees.

[matejdro]

Thanks for the explanation, made the issue here: https://youtrack.jetbrains.com/issue/IJPL-218088/Optimize-imports-removes-necessary-Dispatchers.IO-import-causing-K-N-part-to-not-compile