Why is Paging3's LoadState and LoadStates not mark...

# compose

[Vaibhav Jaiswal]

Why is Paging3's LoadState and LoadStates not marked @Stable or @immutable, even when it only has vals and no mutable property

After generating Compose Compiler report I can see that its marked as Unstable

unstable loadState: LoadStates? = @static null

I have this Crossfade, which keeps recomposing even when the instance is not changed

Crossfade(targetState = loadState?.refresh) {... }

[Alex]

is it a data class?

[Alex]

does it contain unstable classes (list etc)?

[Vaibhav Jaiswal]

It's Paging3's LoadState and LoadStates class

[Alex]

both Error and Loading are classes, not data classes

[Alex]

they might be new instances every time

[Alex]

not sure about that though, just looked at the manual

[Alex]

what are you doing with that crossfade? Whats the goal?

[Vaibhav Jaiswal]

Based on the loadState, i show loader state, error state or a LazyColumn

[Vaibhav Jaiswal]

Every time I scroll the list even by a very very small amount, The crossfade recomposes

[Alex]

did you use the jetpack compose paging library or the regular one?

[Vaibhav Jaiswal]

The loadStates come from androidx.paging

[Alex]

you should include the paging-compose artifacts too, they add some classes and functions that make paging compatible with jetpack compose

[Vaibhav Jaiswal]

rememberAsLazyPagingItem() come from cash app paging, which is a typealias to androidx on android

[Alex]

are you using kmp?

[Vaibhav Jaiswal]

Yes

[Alex]

kk