Vsevolod Tolstopyatov

@altavir indeed, the buffer size parameter is useless when you are emitting flow with a single element, I wanted to show the general idea. You can tune it in the...

@sdeleuze >On Spring side, the use case is pretty common: you want to chain 2 remote webservices, the first will return a list of IDs and the second will allow...

Daemon coroutines is an option we are currently exploring indeed

This is a by-design behaviour, that might be potentially tricky to figure out behind all the other machinery. Basically, it boils down to the following example: ``` runBlocking { val...

Regarding the particular `callbackFlow` use-case, I'd recommend using the advice from its documentation: >Using [awaitClose] is mandatory in order to prevent memory leaks when the flow collection is cancelled, otherwise...

Thanks for pursuing this. I'm reopening this and will answer later

Thanks for the reproducer. Unfortunately, I don't think we can do much here without a deep understanding of how live edit works, how and what exactly it reloads and how...

The best pointer I can give you to untie this problem further is to look at the simplified piece of the code: ``` runBlocking { withContext(Dispatchers.IO) { 2 } Unit...

So, long story short, `DispatchedContinuation` wraps the original continuation and intercepts its `resume` method -- instead of direct resumption right in the stack, it schedules its execution in the corresponding...

Closing as a third-party problem, feel free to ask any more questions