Rename `run`

There is a confusion between kotlinx.coroutines.experimental.run and kotlin.run functions from stdlib. We should rename the former. A better name is TBD.

[fvasco]

withContext(coroutineContext) looks clear.

withoutCancellation doesn’t seem much clear.

[mtopolnik]

As a user of withContext in an Android project I can add my experience. In a specific example, I have this line:

val nextFrame = withContext(threadPool) { gifDecoder.nextFrame }

(threadPool is a global val in my project, my own threadpool-context)

The name withContext is unevocative. It doesn’t convey the magic of what it will do; more importantly, it doesn’t even signal that it’s about coroutines. The suggestion runIn would solve a lot of issues I have with the current name, even though it may have some other problems.

Why do async and await work well? Simply because people got used to them in other languages and now they are a part of the vernacular. In this light, maybe Kotlin should try to introduce another simple keyword to capture its “sequential by default” policy. One idea that came to mind is is to lean on the paradigm of threads/fibers and see this as “weaving” or “stitching together” different threads in the sequential execution of a single coroutine: execution jumps to the other one and then resumes on the current one.

As a designer of public API myself I’m kind of sorry to have to bring this up, I share your pain 😃