Vsevolod Tolstopyatov

Not many updates, unfortunately. For `Delay` to be useful, it requires a non-trivial rework and rethinking from the ground up, and it's slightly out of our scope right now. Depending...

I think it's time to promote it to delicate: it has its use-cases, but it's easy to misuse, which fits the delicate concept perfectly

Could you provide any reproducer for the scenario where an exception is thrown upstream but is completely ignored?

``` try { flow { emit(1) yield() println("Upstream failure") throw RuntimeException("Upstream flow failing") }.buffer(1).flowOn(Dispatchers.Default) .catch { println("Catch operator: $it") } .collect { println("Downstream throw") throw TestException() } } catch (e:...

@nbransby this is a leaking behaviour of multiple aspects: concurrency imposed by `flowOn`, `catch` operator being able to `emit` and that `first` cancels asynchronous coroutine (e.g. the behaviour won't reproduce...

The root cause that introduced the problem (and fixed other problems): https://github.com/Kotlin/kotlinx.coroutines/pull/3017 (#2860)

Unfortunately, actors are obsolete APIs, and we would like to avoid evolving them further or promoting their usage. Could you please elaborate on the use-case where the actor is allowed...

@sgammon have you succeeded filing an issue against GraalVM? From where we are at, it seems like it's rather a Graal issue than not

We are all for applying the workaround if there is one, but the core issue is on the Graal side and worth addressing here. I believe it still awaits the...

Public issue: https://youtrack.jetbrains.com/issue/KT-54299/Extract-org.w3c-declarations-to-separate-library-from-K-Wasm-Stdlib