Kotlinx.coroutines: Proposal: deprecate "coroutineScope" function and rename it to "runScoped" instead.

[antanas-arvasevicius]

Hi,
I propose renaming of coroutineScope function to runScoped.

• Currently there is some confusion between runBlocking and coroutineScope and by observation seems many people thinks that coroutineScope is like launch (not blocks / suspends), maybe by renaming function to runScoped would help to associate it with runBlocking and helps to know(feel) that this call is also blocking / suspending.
• Current name coroutineScope is a noun and feels like it would create a block of scope and returns it, but actually it runs a given block and returns block's result value, runScoped will reveal intention more clearly.
• And there are too many "coroutinescope" definitions now, fun CoroutineScope(), interface CoroutineScope.

[gildor]

I completely agree this function is the main source of confusion in coroutines channel of Kotlin slack the last few months.

Some time ago I proposed another name awaitScope, but probably runScope is better name 👍

[adibfara]

I do agree with the confusion that It makes. Although something other than run might be better.

[streetsofboston]

Maybe joinScope is a good name?

[Tougee]

I agree with this confusion name and prefer a name like runBlockingScope, this kind of name can emphasize this call will block the coroutine like the runBlocking block the current thread.

[elizarov]

Any use of the word "blocking" is completely out of the question. To avoid confusion we explicitly reserve the word blocking for cases when the thread is block and use the term "suspension" to refer to case when coroutines wait for anything without blocking a thread.