A modern programming language that makes developers happier.

kotlinlang

:kotlin-intensifies-purple::tada: 
*Kotlin 1.8.0-Beta* brings the following updates*:*

:white_check_mark: Gradle 7.3 compatibility
:white_check_mark: Recursive `Path` utility functions in the stdlib
:white_check_mark: Support for Xcode 14 in Kotlin/Native
:white_check_mark: Discontinuation of support for the old JVM backend

Try it out and share your feedback!
:point_right: <https://kotlinlang.org/docs/whatsnew-eap.html>

Is there more info about the `kotlin.mpp.androidSourceSetLayoutVersion=2` addition?
Doesn’t seem to have more info on what it does exactly.

<https://youtrack.jetbrains.com/issue/KT-53342/TCS-New-AndroidSourceSet-layout-for-multiplatform|https://youtrack.jetbrains.com/issue/KT-53342/TCS-New-AndroidSourceSet-layout-for-multiplatform>

I would imagine that there's no Compose version compatible with this, correct?

As always, check the dev builds for the latest and greatest as I mention here <https://kotlinlang.slack.com/archives/C0922A726/p1668080970967089?thread_ts=1668080842.149499&amp;cid=C0922A726|https://kotlinlang.slack.com/archives/C0922A726/p1668080970967089?thread_ts=1668080842.149499&amp;cid=C0922A726>

Hm, I currently use Kotlin 1.7.20 with Gradle 7.5.1. Does it mean that I should downgrade to a Gradle version before 7.3?

From what I understand, this is mainly about not creating task eagerly (see <https://youtrack.jetbrains.com/issue/KT-52624|KT-52624>). So it should be fine staying on Gradle `7.5.1` . What you should see is faster builds

_slightly_ faster. I wouldn't expect an order of magnitude change but still a tiny bit faster

&gt; Hm, I currently use Kotlin 1.7.20 with Gradle 7.5.1. Does it mean that I should downgrade to a Gradle version before 7.3?
No, Kotlin Gradle plugins works fine with newer Gradle versions. In Kotlin 1.8.0 we are declaring full support for Gradle 7.3 meaning you should not see Gradle deprecation warnings and plugins should support newly added Gradle features.

For me it's this one I'm looking forward. :slightly_smiling_face:

<https://youtrack.jetbrains.com/issue/KT-47355/Support-macos-target-for-FatFramework-task>

I remember that people at my old job were waiting for Lombok @Builder support. Not having that made the Kotlin conversion of their existing Java projects cumbersome.

regarding the full support for Gradle 7.3 thing, doesn't the Gradle plugin use hardcoded Kotlin 1.6.21? I seem to remember having read this not too far back.

Gradle Kotlin runtime version is not related directly to Kotlin Gradle Plugins

sorry for being slow (or simply not understanding Gradle Kotlin Plugin enough), but you wrote this change was about Gradle deprecation warnings no longer being shown. But if the Gradle itself uses Kotlin 1.6.21, will it not still display those warnings?

Kotlin Gradle plugins could use some Gradle APIs that were deprecated in newer Gradle versions. For example, when you are running build with Gradle 7.5 and KGP 1.8.0 - you probably may see "Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.". Newer KGP releases are fixing this deprecations so you should not see such message and your migration to Gradle 8.0 should happen smoother.

I'm going on hunger strike until we get test-fixtures in android library projects /s