Vsevolod Tolstopyatov
Vsevolod Tolstopyatov
Thanks for the proposal! Could you please elaborate why is it unexpected behaviour? E.g. why one may expect to use `runCatching` that actually rethrows **some** of the exceptions? What are...
`delay` behaves exactly according to its documentation: >There is a **prompt cancellation guarantee** If the job was cancelled **while this function was suspended**, it will not resume successfully This is...
Hi, I'm still processing your input and trying to internalize all the things in order to further weigh the pros and cons of the solution. Let's discuss individual details in...
Could you please provide a compelling use-case for this operator? E.g. an example of a problem you want to solve with this operator
Could you please explain a bit your use-case? E.g. what kind of domain-specific problem you would like to solve with such operator
Thanks, we'll take a look at some point closer to the next release. It would be really great if you could pinpoint the issue, at least partially, to speed-up the...
It seems to be https://youtrack.jetbrains.com/issue/KT-53243/Native-data-race-in-lazy-initialization fixed in 1.7.20. Please update to 1.7.20 when it's released (or 1.7.20-RC if that works for you) and the issue should be gone
The same issue is also present in `TimeoutCancellationException` and `AbortFlowException`, added a generic check for throwables
Could you please point out the test which I should run in order to reproduce the crash? Or should I launch the app and click somewhere?
Thanks! The reason was the diagnostic exception that was itself serializable, but transitively got non-serializable `StandaloneCoroutine`