Hi! I have a stupid question about coroutines. So ...

# coroutines

[ahulyk]

Hi! I have a stupid question about coroutines.
So we have Channels - hot streams and Flows - cold streams.
The question is: if we converting Channel into Flow - we are getting kind of 'hot' Flow???

[gildor]

Yes, you accessing hot channel using cold API, same with Subject in Rx

[ahulyk]

@gildor thanks, cool 😎

[ahulyk]

@gildor in general overall idea and api looks just perfect 🙂 👌

[gildor]

Also, soon we will get DataFlow (which is observable data holder with Flow API) which is essentially a hot Flow

[gildor]

so I wouldn’t focus too much on this, because it’s not so strict semantics, also should be clear separation between hot and cold nature of stream and API that used to consume it

[streetsofboston]

@gildor Would the introduction of DataFlow mean Channels may no longer be necessary? Or would they still be preferred for certain programming constructs?

[gildor]

ConflatedBroadcastChannel will be not necessary (or at least I don't know other usecases for it, maybe some more specific), but other types of channels are important low level primitives (and used also for Flow, even in public API like callbackFlow)

[streetsofboston]

Sorry, yes, I see the need for using them in low level implementations.

But would they still be needed for higher level implementations, for app development?

[gildor]

for own high level primitives, operators for flow etc

[gildor]

but probably not for everyone

[gildor]

Flow just safer and easier to use

[streetsofboston]

👍