Profile avatar
jorgecastillo.dev
Android at Disney+. Author of Jetpack Compose internals. 📖 Compose book jorgecastillo.dev/book 👨‍🏫 Compose course jorgecastillo.dev/course
119 posts 1,528 followers 245 following
Prolific Poster
Conversation Starter
comment in response to post
Every time it gets full during composition, it doubles its size. This process has linear time (O(n)) since it needs to copy all groups from the table, but this normally happens only once or twice per tree at most. The size is normally big enough pretty early to hold the whole tree on all its states.
comment in response to post
For a more detailed post with examples around this, check this post from my friend Tomáš Mlynarič medium.com/androiddevel...
comment in response to post
Yeah definitely. I can see people can get confused. Will update it.
comment in response to post
It’s a different thing. That post mentions that adding it to the “whitelist” configuration file is same as flagging it as Stable, so two instances of it are compared using equals. Strong skipping does not do that, collections remain unstable and compared with ===.
comment in response to post
Lol. Yes, I meant for conversations where only devs are involved. I also call them components otherwise.
comment in response to post
Wow.
comment in response to post
Thanks, more please.
comment in response to post
There is always value on sharing your point of view, experience and learnings on anything.
comment in response to post
Good job! ❄️
comment in response to post
It’s definitely not the best UI for that.
comment in response to post
Kotlin collections can be the most common case. They will rarely be the same instance, even if the data they contain has not changed.
comment in response to post
I just cross post the Android stuff.
comment in response to post
Strong skipping compares unstable classes with referential equality. If your mappings ends up creating a new class every time, even if the data does not change it will still recompose. Source developer.android.com/develop/ui/c...
comment in response to post
That’s a proper explanation 😆 Jokes aside, I imagine there is not a difference between edge to edge now and in old system versions. Same implications.
comment in response to post
Yep indeed, but that option will not last forever.