Roman Elizarov

Every operator should be functionally implementable via some public API. Internal API is only needed for highly-efficient (optimized) implementations. In particular, `throttleFirst` is relative easy to implement. See here quite...

@fjna You'll need additional code to support `TestCoroutineScope`. Instead of using `System.currentTimeMillis()` you shall use the following snippet: ``` val time = (coroutineContext[ContinuationInterceptor] as? DelayController)?.currentTime ?: System.currentTimeMillis() ``` As for...

@zach-klippenstein Yes. Created a separate issue for it: #1499

> Is there any activity related to this issue going on 😄 ? Not yet.

@Anton-Spaans-Intrepid Let's take a look at a more realistic example, please. What are the use-cases for `runCatching` in an application code? Can you give a code snippet that motivated you...

@mboudraa How `Flow` is useful in your case of http api calls? For concurrent calls we have the following idiom: ``` coroutineScope { // make the calls concurrently val d1...

Thanks. This kind of operator would be called `chunked` in Kotlin lingo. Thanks for spelling out a use-case with a time-limit chunking. See #1290 for a size-limited use-case.

Before we delve into the design we need to need to gather and discuss use-cases. @circusmagnus has great use-cases which call for `maxSize` and `duration` chunk constraints. I am not...

It is trickier to reproduce. You need a wrapped exception. The root cause of the problem is that `JobCancellationException` keeps a reference to a `Job` which is, in general, not...

Thanks. There's already PR with a fix for the next release: #2437