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
s

Stylianos Gakis

06/09/2022, 7:10 AM
I know when we need to remember something that doesn’t need to then be mutated, we can simply wrap it in a remember without the mutableStateOf, like
val item = remember(someKey) { ExpensiveConstructedThing() }
instead of
val item by remember(someKey) { mutableStateOf(ExpensiveConstructedThing()) }
However after reading about this very informative article and some official docs, to my understanding when we use
by
on the state object, we get the neat effect of not reading the value at that moment, but deferring the read to whenever we actually need it. Which sometimes comes with the nice side-effect or reading that state object in a “smaller” recomposition scope meaning that when it changes we don’t invalidate the wider recomposition scope that the above definition may be in. So if we do not do this, but use simply
val item = remember(someKey) { ExpensiveConstructedThing() }
do we lose this nice side effect? When
someKey
does change, and the result of
item
changes with it, will it invalidate the recomposition scope in which it is declared in as opposed to where it is actually read?
👀 2
a

Albert Chang

06/09/2022, 7:39 AM
The effect only happens when the change happens in the same
State
instance. With
val item by remember(someKey) { mutableStateOf(ExpensiveConstructedThing()) }
you won’t get the effect anyway because the
State
instance itself changed.
k

krzysztof

06/09/2022, 8:57 AM
I’d suggest to read the next chapter of Zach’s article, here: https://dev.to/zachklipp/remember-mutablestateof-a-cheat-sheet-10ma It’d explain the
by
here (property delegation) more clearly. TL;DR: it’s the same as using
state.value
s

Stylianos Gakis

06/09/2022, 9:02 AM
Yeah I have read it, and I understand that it’s “just” a
state.value
but the important bit is that this read is deferred to when you actually use the value for the first time instead of on the declaration line, which means that when reading it you are likely to be in a smaller recomposition scope therefore invalidating only that instead of the entire thing.
k

krzysztof

06/09/2022, 9:05 AM
👍 It’d be the same case in both examples, as you “read” the state value by calling
myState.value
if not using delegate, while with delegate you just call
value
s

Stylianos Gakis

06/09/2022, 9:07 AM
Albert let me try and understand. Is the State instance different since the remember key would be changed therefore it creates a whole new State instance with the new call to mutableStateOf()?
a

Albert Chang

06/09/2022, 9:08 AM
Exactly.
s

Stylianos Gakis

06/09/2022, 9:10 AM
Awesome, thank you! So in this case, even if I declare this line at the top of my composable but I then read it inside a smaller recomp scope, it would still invalidate the entire scope no matter what I do right?
👍 1
a

Albert Chang

06/09/2022, 9:11 AM
Yep.
🙌 1
s

Stylianos Gakis

06/09/2022, 9:22 AM
And Krzysztof, I don’t know if I don’t understand you or if you don’t understand me, but I think we’re not referring to the same thing. I was referring to in which recomposition scope a state value is read, you’re just describing the difference between using a delegate and not using it. Your “TL;DR: it’s the same as using `state.value`” is only half true as it has implications on how often things recompose. Which is also why using the destructuring approach is not equivalent to using the delegate approach. Not about correctness, but performance.
k

krzysztof

06/09/2022, 9:27 AM
Yeah, I misunderstood totally what you meant, that’s on me 😅
is only half true as it has implications on how often things recompose.
I’d be interested in seeing an example of it - you say using delegate approach would trigger less recompositions than property access approach?
It looks like the delegating extension function on State does nothing special than just calling
value
on receiver, hence I said it’s the same thing
s

Stylianos Gakis

06/09/2022, 9:43 AM
Yes, this article called donut-hole skipping happens to explain how recomposition scopes work and how reading a State object inside a smaller scope invalidates only that scope and not the scope in which the variable was declared in. I don’t have a working sample but if you change the
val counter by remember { mutableStateOf(0) }
to
val (counter, setCounter) = remember { mutableStateOf(0) }
then it will invalidate the scope in which this line is declared on, not just in which it is read in. With all that said, now that I see what you said again better, if you do use just
val counter: State<Int> = remember { mutableStateof(0) }
and you read it with counter.value in the same scope, then it is equivalent yes. When you were saying = and by are the same thing I was immediately thinking of using the destructuring declaration, as I’ve almost never seen someone use the
=
syntax and keeping a hold of a
State
object, since that’s imo the least convenient of all the approaches 😄
👍 1
k

krzysztof

06/09/2022, 9:50 AM
haha, that make a lot of sense now 😄 Yes, in case of descructuring, it make sense that state value is read immediately in line it’s being declared in, so it’s wider scope that’s get recomposed
s

Stylianos Gakis

06/09/2022, 9:52 AM
Yeah I am glad we understood each other, sorry for making this wrong assumption before 🤗
🙌 1
z

Zach Klippenstein (he/him) [MOD]

06/09/2022, 3:15 PM
The only “reads” that compose cares about, or even knows about, are reads of snapshot state objects. Those are the only reads that can invalidate composition. If you instantiate a class with some non-snapshot-state-backed properties, then read those properties, that will never invalidate the composition.
🙌 1