https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
a

Alex

10/13/2020, 9:53 AM
Hey is there a non-state version of
MutableStateFlow
? I have been using
ConflatedBroadcastChannel
, but would like to move to flow completely. I know there is
Flow
itself, but I have not found a way to send values to it from outside the creation lambda.
k

KamilH

10/13/2020, 9:59 AM
Can’t you just expose
MutableStateFlow
as
Flow
? The former one implements the latter, so you can do it by just casting
m

Marc Knaup

10/13/2020, 10:13 AM
The problem is that MSF requires an initial value. Apart from converting a Channel into a Flow you can create your own AbstractFlow implementation 🤔 But behind the scenes many Flows are implemented using Channels, as they’re perfectly fine for that.
g

gildor

10/13/2020, 10:24 AM
you also can just use StateFlow with initial null and filter it before returning from your class
m

Marc Knaup

10/13/2020, 10:31 AM
Also good in cases where
null
is not a valid value. In that case you could make your own
val undefined = Any()
and filter that out.
a

Alex

10/13/2020, 11:45 AM
So are Channels going to be deprecated in favor of
Flow
?
m

Marc Knaup

10/13/2020, 11:46 AM
No, they still have their purpose.
Regarding a non-state Flow like
MutableStateFlow
note that here is another difference between using a Channel and a hidden `StateFlow`:
StateFlow
is conflating, i.e. it drops intermediate results if the collector is slow.
👍 1
a

Alex

10/13/2020, 11:47 AM
So I guess using
ConflatedBroadcastChannel
and then calling
.asFlow()
would still be my best bet. Maybe I can wrap that in a version of
AbstractFlow
and call it
MutableFlow
to keep with the definitions.
m

Marc Knaup

10/13/2020, 11:49 AM
What’s the use case btw?
a

Alex

10/13/2020, 11:51 AM
The use case is Android state management. For View-State
MutableStateFlow
works perfectly fine, it’s a fantastic addition. But there are some things that should not be retained as states but still emitted (usually called effects), for example Toast messages (small messages shown once). For this a non-stateful
Flow
works, but it has to be able to be triggered from the outside. If you used
MutableStateFlow
for effects then you would show a toast message and then upon phone rotation would show the same toast message again, which is not required.
👍 2
AbstractFlow
is actually only for stateful
Flow
implementations:
Base class for stateful implementations of `Flow`.
Would this be safe to do?
private lateinit var effectsEmitter: FlowCollector<Effect>
    val effects = flow<Effect> {
        effectsEmitter = this
    }
m

Marc Knaup

10/13/2020, 11:55 AM
Not really. You’d use
FlowCollector
from the wrong coroutine context and likely raise an exception.
Also, every new collector would overwrite the previous
effectsEmitter
. So if you have multiple collectors for the flow they break each other.
👍 1
a

Alex

10/13/2020, 11:57 AM
I think this is probably the best approach then until there is some non-stateful official version of
Flow
private val _effects = ConflatedBroadcastChannel<Effect>()
    val effects: Flow<Effect> = _effects.asFlow()
👍 1
m

Marc Knaup

10/13/2020, 12:02 PM
Where are the Effects coming from? Why isn’t the source a Flow?
a

Alex

10/13/2020, 12:57 PM
that’s good food for though. It could be anything. Could be a flow, could be a button click, could be some legacy code, could be some third party plugin.
m

Marc Knaup

10/13/2020, 12:59 PM
Button clicks can also be flows 🙂
Looks like Channels stay but BroadcastChannels will go away. Upcoming change: "* Future deprecation notice for BroadcastChannel, ConflatedBroadcastChannel, broadcast, and broadcastIn."
a

Alex

10/13/2020, 1:56 PM
Hmm so what could I replace the
ConflatedBroadcastChannel
in the example above with?
Still, we cannot rewrite everything to be a flow in a week, we need some layer in between 🙂
I found this: https://github.com/Kotlin/kotlinx.coroutines/issues/2034 Which looks like exactly what I need. Going to be released in 1.4.0
👍 1
g

gildor

10/13/2020, 2:11 PM
Broadcast channels will be there for a quite long time, they not even deprecated yet