Allow indirect calls to suspendable methods about kotlinx.coroutines

[cypressious]

Yes, runBlocking blocks, as the name suggests. Alternatively, use launch to start a coroutine without waiting for it. In any way, you can't just call suspend functions from non-suspend functions because they are compiled completely different. That's just how coroutines work.

[cypressious]

While this issue probably for Youtrack, I'll answer here:

You can always do runBlocking<Unit> {} in your non-suspend functions to cross the boundry to the coroutines world.

[ufoscout]

@cypressious the workaround you propose is not the same, in fact, if I am not wrong, runBlocking<Unit> {} blocks the calling thread.
In addition, it uses a different context than of the one of the caller and it should be used only as top-level coroutine based on the documentation:

runBlocking { ... } works as an adaptor that is used here to start the top-level main coroutine. The regular code outside of runBlocking blocks, until the coroutine inside runBlocking is active.

[elizarov]

It is not just the different compilation. Suspending and non-suspending functions are conceptually different. suspend function can suspend the execution, while regular functions cannot do it conceptually. Think about it as a part of a function's type. For example, if your function is declared to return a String it cannot just go ahead and return an integer 32 instead. Similarly, if your function is declared with a guarantee that it never suspends (a regular function), it cannot just decide go ahead and decide suspend. That is so by design.