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
l

Lilly

11/09/2021, 11:07 AM
Maybe a trivial question, but I often see people using
flow
operator for functions returning a single value. What's the purpose of doing this? Are there any benefits by doing this?
m

mbonnin

11/09/2021, 11:09 AM
Makes it easier to use Flow operators like
retry
,
catch
, etc...
l

Lilly

11/09/2021, 11:10 AM
But if I don't need those, it wouldn't make any sense right?
b

Big Chungus

11/09/2021, 11:12 AM
It would for consistency. If you use flow elsewhere, your code will be much easier to parse and reason about if everything is done with flows
But that comes down to preference I guess
l

Lilly

11/09/2021, 11:13 AM
Good point, thanks 🙂
m

Marko Novakovic

11/09/2021, 11:19 AM
+1 to Martynas, also if you use libraries like… let’s say Room, that return single value but if you ask for
Flow
it will update regularly whenever dat changes. maybe you overlook something. sometimes people use it just because it looks cool, best to evaluate your own usecases
👍 2
l

Lilly

11/09/2021, 11:21 AM
sometimes people use it just because it looks cool,
Yeah that's what I also thought first 😄
m

Marko Novakovic

11/09/2021, 11:22 AM
true 😄, looks cool and it’s latest hot topic in the community
m

mbonnin

11/09/2021, 11:23 AM
Sometimes it can be cold too ahah!
😂 7
l

Lilly

11/09/2021, 11:33 AM
😏
y

yschimke

11/09/2021, 1:45 PM
The cold point is valid, it's more powerful and arguably nicer API than a suspending function.
a

Adam Powell

11/09/2021, 1:53 PM
If you want cold factories for an operation,
suspend () -> T
is right there
3
👌 1
j

Joffrey

11/09/2021, 2:20 PM
Yeah honestly I don't buy the "flow for everything" approach at the moment. Suspend functions are really convenient. The caller can completely control how it's called. If you don't need an actual subscription with value updates, I don't quite see the point in using flow. It feels more like people coming from Rx are trying to match that model, rather than an actual convenience.
2
👍 4
It would for consistency. If you use flow elsewhere, your code will be much easier to parse and reason about if everything is done with flows
@Big Chungus I do believe the opposite of this, so I guess yeah it's matter of preference. Using flows everywhere you can't know anymore what's supposed to give you a single value, or if this will be updated in the future and more values may come.
👍 5
m

mcpiroman

11/09/2021, 2:30 PM
It is kind of as using `Any`everywhere for consistency
👍 4
a

Adam Powell

11/09/2021, 2:54 PM
Or the Rx analogy, it would be like using
Observable
everywhere for consistency, even in places where
Single
or
Maybe
are a better fit
l

Lilly

11/09/2021, 3:05 PM
Hmm also good points from @Joffrey Thanks for your thoughts
y

yschimke

11/10/2021, 8:39 AM
I think the flexibility/ambiguity of flow is a feature, the API doesn't need to change later when you do find you need to subscribe for changes, but it's trivially convertible back to suspend with flow.first()
I had a ViewModel with a cache User. A MutableState, that I populated with a coroutine launched in viewModelScope. I removed the State, just exposed the Flow, but annoyingly found it glitchy as each view would relaunch the flow. Suggestion from a coworker and glitch solved.
val me = dao.getMe().shareIn(viewModelScope, SharingStarted.WhileSubscribed(5000))
j

Joffrey

11/10/2021, 10:41 AM
We might be talking about different things then. I mean that I really don't want to expose a flow that is defined this way:
flow { emit(callSuspendStuff()) }
. In this case, just expose the suspend function. If your function does support update events, then expose a
Flow
of course. And users can use the first value if they want, or subscribe for more. But if the flow is defined to emit only one element, this is basically lying in the API.
Regarding your bug in the view model, I didn't quite get how it relates to the topic. If the UI needed reactive updates, then you should indeed be using flows. But that's not really about the design of the lower APIs.
y

yschimke

11/10/2021, 2:01 PM
Good, point I lost the context of single value. But arguably, starting with an assumption of reactive flows all the way through, let's you handle the simple case, but also support reactive backends like Room also.
d

darkmoon_uk

11/11/2021, 1:29 AM
If I have a single asynchronous value, I'll default to representing that as a suspending function; but if it makes practical sense to bring that fully into a 'reactive system' as a
Flow
then that's okay too - it's not just to look cool 🙂
I mean; it's not just to look cool 😎
l

Lilly

11/23/2021, 4:41 PM
Thanks for your input guys 🙂