3040172: Make strong skipping non-experimental | <...

# compose

[Sergey Y.]

3040172: Make strong skipping non-experimental | https://android-review.googlesource.com/c/platform/frameworks/support/+/3040172

Hmm, and it looks like it will be enabled by default as well, if I'm not mistaken. 👀

[Stylianos Gakis]

The PR says “It will be enabled by default in a future release.” so probably not yet

[Sergey Y.]

Google IO announcement time?

[Sergey Y.]

Along with a new JB Compose Compiler that replaces the Google Compose Compiler

[Stylianos Gakis]

Could be, but definitely need to have it out there without it being experimental so more people adopt it before they just turn it on by default

[Sergey Y.]

Any chance for Compose-2.0-alpha01 with Kotlin 2.0, new JB Compose Compiler, Strong Skipping Mode? 👀

[efemoney]

Highly doubt it. Why would Compose jump to 2.0? 🤔

[Sergey Y.]

To align the versions with the compiler and language toolchain it is bound to.
This sounds reasonable to me.

[efemoney]

Kotlin 2.0 is a complete overhaul of the internals of kotlin (plus its riding on the heels of a 1.9 release). Makes sense for that to change.

Compose will not jump to 2.0 because while the compiler can change understandably with Kotlin (compiler API & language capabilities), those changes mean nothing to the API of compose runtime & libraries.

[shikasd]

Fwiw, Compose compiler will have the same version as Kotlin when Jetbrains will publish it, but Compose runtime will continue on it 1.x increments

[shikasd]

Also strong skipping will not be enabled by default with 2.0, just because we don't want to rock the boat even more
With the new compose gradle plugin (it is published together with Kotlin Compose compiler version now) you should be able to easily configure it to be enabled though