Pavel Chervakov

Please remember to consider natural batching use-case (#902) in the design. How to express "emit chunk always immediately as soon as possible" in the proposed API? Basically to buffer upstream...

I was more thinking along the lines of what @elizarov suggested [in this comment](https://github.com/Kotlin/kotlinx.coroutines/issues/902#issuecomment-537500657): _duration is set to zero and size limit is set to very big value_ I think...

> Do you think that last case `CollectorIsReady` needs max size customization option? Perhaps someone would like to have a time constraint there too? Not really. Time constraints are direct...

@circusmagnus I am waiting for clarification [here](https://github.com/Kotlin/kotlinx.coroutines/issues/902#issuecomment-728056185) before discussing it further.

> So basically we are postponing this feature until #254 and then we (probably) will be able to provide a consistent API for both cold and hot streams. We will...

> > > I think we can manage to implement it as part of #1302. That is, a single `chunked` operator that supports a duration and size limit parameters should...

Good point about return type @jGleitz, don't know how I missed that. Chunked will have a List in the return type by design. However the question about `chunked` being fully...

@schikin As far as I can tell your snippet does simple size-base chunking. The issue is about natural batching which is very different.

@arberg At least I understand it this way and think it is correct. We are on the main thread launching a coroutine to be dispatched later on the same main...

Wow, it does work in jep console for me too! Any ideas what could be different between console and my application? I can't find anything suspicious in my code or...