Vsevolod Tolstopyatov
Vsevolod Tolstopyatov
I think we will address this issue right after Kotlin 1.3.60 release (along with #1596)
Long story short, I was trying to rewrite the dispatcher with proper locks (i.e. https://github.com/Kotlin/kotlinx.coroutines/commit/c414dce40d749436d1681f8fac8ad47fe2f2b17b) in order to make it faster. Apparently, zero-contention cases indeed become significantly faster, but any...
On a side note, the documentation to the native declaration of `newFixedThreadPoolContext` will arrive later, first, we'll merge it, and I'll create `Dispatchers.IO` on top of that and only then...
The fix looks good to me
The rationale behind the current behaviour is the following: * We do not consider `withContext` semantically as creating a new coroutine. We do consider it a natural continuation (sorry for...
That's a great suggestion, we definitely will be looking towards that. It fits perfectly with our idea of orthogonal and composable operators that can be used to express any other...
Makes sense. The biggest blocker was its non-linearizability for buffered channel, but its unlikely to bother anyone and can be changed even in minor release
Do we have any evidence that `LimitedDispatcher` overhead is non-eglible or is it rather a "nice to have" enhancement?
Unfortunately, we are not ready to accept patches right now because the scheduler is being actively reworked. But it would be really helpful if you could provide a more detailed...
>Interesting — is there a branch or design doc or something for the reworking? Curious how it's changing. No for both, though changes will be, of course, properly documented. But...