Call it

blockBlock

, a verb and a noun. Problem solved.

cedric: this whole thing with nouns-vs-verbs is not clear to me

I'm actually wondering why we need runblocking... If it's running on the current thread, it's like it's inline code, isn't it? What's the difference between the code without that keyword?

@kenkyee Does this section answer your question? https://github.com/Kotlin/kotlinx.coroutines/blob/master/coroutines-guide.md#bridging-blocking-and-non-blocking-worlds

@voddan I agree. I think it's important to try and be consistent by default (e.g.

Optional

from Java makes more sense than

Option

of Scala) but you shouldn't try to take this too far. To me,

runBlocking

is perfectly acceptable.

@cedric sooo, you don't see a big deal having

runBlocking

instead of

blocking

?

Not really

oh, ok. It is just that I was trying to express why I don't see a good enough reason to have an uglier

runBlocking

@voddan I think they're equal.

blocking

looks prettier, but

runBlocking

is clearer. Both of those claims are opinions though, so getting everyone's opinion on the matter is valuable.

Ahhh...I see...Runblocking is just to make it explicit. One of the things that is not obvious with c# async await is that an async method is blocking into you hit the first await. This is the same thing...