Hello Everyone, Few months earlier when Compose wa...

# compose

[Shabinder Singh]

Hello Everyone,
Few months earlier when Compose was still alpha and a lot of performance improvements were being made,
two things were there I wanted to know about and whats their status

• Inlining Composable components was also being talked about , what happened to that ?
• Multi-threaded Composition ?
🤔

[Zach Klippenstein (he/him) [MOD]]

There are lots of inline components (eg Layout, and most of the standard layouts like Box, Column, etc)

[Zach Klippenstein (he/him) [MOD]]

Multi threaded composition is still being worked on

[Adam Powell]

Yep. In particular multithreaded composition is mostly waiting until some other runtime features that heavily impact data dependencies take further shape, like the composition as a value feature that is intended to allow moving stateful chunks of a composition around. Since it's not clear what composables use subcomposition under the hood and we'd like that to be mostly transparent to user code, that means composition as a value needs to be able to move sections of a composition across different compositions of the same type, which creates a data dependency between those compositions that will affect multithreading.

[tad]

Like a curried function?

[Fabio]

joining this convo a bit late, but I think there's some contradiction here

Compose can optimize recomposition by running composable functions in parallel. This lets Compose take advantage of multiple cores, and run composable functions not on the screen at a lower priority.

<https://developer.android.com/jetpack/compose/mental-model?authuser=2&continue=https%3A[…]2Fdeveloper.android.com%2Fjetpack%2Fcompose%2Fmental-model>
so what does that mean exactly?