Is there any reason that `channelFlow` doesn t expose someth kotlinlang #coroutines

Channels

lincheck

kobweb

koalaql

kotlin-multiplatform-contest

osgi

brikk

revolver

tricity-kotlin-user-group

cincinnati-user-group

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

androidgithubprojects

navigation-architecture-component

stayhungrystayfoolish

practical-functional-programming

tensorflow

swagger-gradle-codegen

kotlinultimatechallenge

competitive-programming

skia-wasm-interop-temp

java-to-kotlin-refactoring

event21-community-content

myndocs-oauth2-server

jvm-ir-backend-feedback

Title

kevin.cianfarini

02/10/2020, 3:53 PM

Is there any reason that

channelFlow

doesn't expose something like

fun channelFlow(buffer: Int = ...)

And instead we have to call

.buffer

downstream?

👀 1

Zach Klippenstein (he/him) [MOD]

02/10/2020, 4:02 PM

It would be confusing to have code that looks like:

channelFlow(buffer = UNLIMITED) {
  …
}.conflate()

Because the two buffer specifications would compete (since the operators are fused under the hood and use a single channel), and only one of the specifications would actually be used.

kevin.cianfarini

02/10/2020, 4:03 PM

The missing piece I had was that operators are fused.

knowing that solves this question

here's the bit in question

return if (this is ChannelFlow)
        update(capacity = capacity)
    else
        ChannelFlowOperatorImpl(this, capacity = capacity)

👍 1

and from the docs for anyone who reads this later

Adjacent applications of channelFlow, flowOn, buffer, produceIn, and broadcastIn are always fused so that only one properly configured channel is used for execution.

👍 2

#coroutines Join Slack