:mega: :rocket: :tada: Kotlin 1.6.0 has been relea...
# announcements
a
📣 🚀 🎉 Kotlin 1.6.0 has been released with: K Language features: • Sealed (exhaustive) when statements • Suspending functions as supertypes • Improved type inference for recursive generic types, and more   Kover, a new code coverage Gradle plugin 🧠  An experimental new memory manager for Kotlin/Native Please read the blog post to learn what else is new in Kotlin 1.6.0.
🤙🏾 1
🦜 23
👍🏼 1
🤙 3
👌 6
🦜 14
K 34
🎉 45
🇦🇲 3
K 116
👍 12
❤️ 11
n
I hope that Compose support will follow soon 🙂
18
g
Migration on Kotlin 1.6 already merged to compose, so now waiting for compose release with those changes
🙏 2
👍🏻 2
👍 3
🙏🏽 1
r
Starting with Kotlin 1.6.0, you can now develop using three previous API versions instead of two (along with the current stable one). Currently, this includes API versions 1.3, 1.4, 1.5, and 1.6.
Nice, this makes the adoption of Kotlin easier for projects where a slow update cycle is preferred over latest-greatest 👍
e
Compose now works with Kotlin 1.6.10. • Upgrade Kotlin to 1.6.10 • Upgrade all compose dependencies to 1.1.0-beta04 • set kotlinCompilerExtensionVersion = "1.1.0-beta04" I had to to set
suppressKotlinVersionCompatibilityCheck=true
as well:
Copy code
tasks.withType<org.jetbrains.kotlin.gradle.tasks.KotlinCompile> {
    kotlinOptions {
        jvmTarget = "1.8"
        freeCompilerArgs = listOf(
            "-Xallow-jvm-ir-dependencies",
            "-P",
            "plugin:androidx.compose.compiler.plugins.kotlin:suppressKotlinVersionCompatibilityCheck=true"
        )
    }
}
Without that flag it complained:
This version (1.1.0-beta04) of the Compose Compiler requires Kotlin version 1.6.0 but you appear to be using Kotlin version 1.6.10
When I switched to Kotlin 1.6.0 I got:
This version (1.1.0-beta01) of the Compose Compiler requires Kotlin version 1.6.10 but you appear to be using Kotlin version 1.6.0
🤦‍♂️ I assume some other dependency is using 1.1.0-beta01
g
Compose 1.1.0-beta04 without flag works with 1.6.0 for our project Maybe you have 2 different compose configurations in different modules?
a
1.1-beta04 works with 1.6.0. If you got warning about 1.1.0-beta01, probably you have some other deps on it
e
yes I'm using Jetbrains Compose, 1.0.1-rc2 of the plugin asks for 1.6.10 while the compose compiler needs 1.6.0 so disabling the version check seems to be the way forward for me