Will the compose compiler support 1.8.0 anytime so...

# compose

[zt]

Will the compose compiler support 1.8.0 anytime soon? I know there's dev release but I would prefer to use the regular androidx release

[hfhbd]

Option 1: Wait for the official release. AFAIK this will take 2 weeks because the last release train was missed: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1673535736890999?thread_ts=1673534078.539299&cid=CJLTWPH7S
Option 2: Use a dev release.

[zt]

Ah ok, thank you

[Jakub Syty]

@hfhbd i think last time (for 1.7.21) compiler was released out of schedule, but i might be wrong

[Jakub Syty]

yup, i think it was:

[Paul Woitaschek]

Wasn’t the point of decoupling the compiler from the rest so that we can get a speedy release? To me it’s always a bummer when we have to wait so long until we can make use of the latest kotlin version

[Jakub Syty]

I'm sure they are doing everything they can. The kotlin compiler plugins isn't stable feature, there are no api guarantees. It's not that simple. There were able to do quick bumn on 1.7.20, but 1.8 introduces a lot of compiler changes. They have to work it all out

[Paul Woitaschek]

I was noting that it seems that the KSP is able to release compatible versions quickly (one day) after a new Kotlin release, and that they test on release candidates. I was curious if a similar approach could be taken for Compose, in order to make it available for the latest Kotlin version as soon as possible.

I apologize if my previous message came across as negative, I’m just curious about the process.

[Jakub Syty]

Compose is far more complicated since they are actively rewriting existing functions

[Jakub Syty]

KSP is using compiler just to access types, but it does not interfere in existing code

[Jakub Syty]

so i guess regression testing in compose compiler has to be very hard

[Jakub Syty]

since they might just brake people code

[Jakub Syty]

https://developer.android.com/jetpack/androidx/releases/compose-compiler#1.4.0