In 2025.1 EAP, with K2 enabled, parameter name inlay hints are always shown, right? There doesn't seem to be an option to have them only for literals anymore?

💫*The Kotlin 2.1.10 release is out!*kodee greetings Huge thanks to everyone who joined the EAP – your feedback is invaluable! K

K*Kotlin 2.1.20-Beta2 has been released!* For more details, please refer to What’s new: https://kotlinlang.org/docs/whatsnew-eap.html.

JetBrains has joined this channel by invitation from kotlinlang.

@Michael.Lysik has left the channel

I’m testing out Kotlin 2.1.20-Beta2. My JS bundle size increased ~7x (from 1.21mb with 2.1.10 to 8.5mb with 2.1.20-Beta2). Is this a bug? Or is there some build script configuration change I need to make?

Since 2.1.20-Beta1 has experimental support for context parameters, can we get it automatically turned on for the playground? That was done for context receivers before, and I really appreciated that.

K*Kotlin 2.1.20-RC has been released!* For more details, please refer to What’s new: https://kotlinlang.org/docs/whatsnew-eap.html.

@Nikita Krasyuk has left the channel

In my project I’m seeing a pretty strange regression when upgrading to Kotlin 2.1.20-RC. Looks to be a LLVM failure?

e: Compilation failed: Invalid LLVM module
Verification errors:
    Call parameter type does not match function signature!
      %40 = call zeroext i1 @"kfun:io.github.kevincianfarini.monarch.BooleanFeatureFlag#<get-default>(){}kotlin.Boolean-trampoline"(ptr %39), !dbg !1058
     ptr  %41 = call zeroext i1 @"kfun:kotlin#<Boolean-unbox>(kotlin.Any){}kotlin.Boolean"(i1 %40), !dbg !1058
    Call parameter type does not match function signature!
      %78 = call double @"kfun:io.github.kevincianfarini.monarch.DoubleFeatureFlag#<get-default>(){}kotlin.Double-trampoline"(ptr %77), !dbg !1074
     ptr  %79 = call double @"kfun:kotlin#<Double-unbox>(kotlin.Any){}kotlin.Double"(double %78), !dbg !1074

Any tips on where to begin debugging this? Everything works fine in Kotlin 2.1.10.

Me waiting for Kotlin 2.1.20-RC2

oh wait, it is released. I was waiting a message here

🚀

With 2.1.20-RC2 and MPP plugin, a jvm target and the Gradle

java-test-fixtures

plugin, I need to switch from

testFixturesImplementation

to

jvmTestFixturesImplementation

. While it makes sense, shouldn't be there a migration path? And what about to extending the default

testFixturesImplementation

?

Is this the right place to discuss Junie EAP experiences?

kodee excited*Kotlin 2.1.20-RC3 has been released!* It contains a few regression fixes: https://github.com/JetBrains/kotlin/releases/tag/v2.1.20-RC3 You can find more docs here: https://kotlinlang.org/docs/whatsnew-eap.html We are looking forward for your feedback! K

am I understanding correctly that usage of the new

-Xannotation-default-target

option will always mark code produced by this compilation as pre-release? reference: https://youtrack.jetbrains.com/issue/KT-75588/2.1.20-RC-was-compiled-by-a-pre-release-ve[…]e-loaded-by-this-version-of-the-compiler-warnings-despite If so, I think this is actually kind of a major issue because not having that escape hatch means that a large codebase either has to forego

allWarningsAsErrors

or meticulously go change every affected annotation 🤔

Is there an EAP IDEA version with support for context receivers yet? I know I can compile from source, but this'd be more convenient

Any news on when a 2.2.0 EAP version will be out? I need its JS/Native context parameter fixes. Alternatively, is there a way to use "nightly" versions of the Kotlin compiler easily?

Is there an easy way in Gradle to have some kind of flag that changes the Kotlin version? I have a few open source libraries and I'd be willing to have a CI that runs once a week using the latest Kotlin EAP to try to early-detect things going wrong. However, I don't know to set it up on the Gradle side (I'm good on the CI side) Ideally I'd like some kind of

./gradlew -Peap

which runs the build using the latest Kotlin EAP version instead of the stable one

kodee welcoming*Kotlin 2.2.0-Beta1* has been released!

I thought the new EAP release along with the latest IDEA beta would fix the K2 issue where control-shift-space completions don't work? I updated everything, but it's still not working?

kodee excited*2.1.21-RC has been released!*

Is there a way to see the parts of context receivers that are currently available? The closest thing to docs i know of is the KEEP which is more of a proposal than up to date docs. the main difference im seeing is not having the

context(...){ }

scoping function to provide multiple values to the implicit context for calling functions with context params. Is this planned for a future release or has the implementation and plans just diverged from the original KEEP?

@antonarhipov has left the channel

kodee naughty*Kotlin 2.1.21-RC2 has been released!*

K*Kotlin 2.2.0-Beta2* has been released! For more details, please refer to What’s new: https://kotlinlang.org/docs/whatsnew-eap.html.

I realize that 2.2.0-Beta2 doesn't seem to officially mention context parameters (so I understand it may not be working). But when trying to use the newly added

context(...)

functions in the standard library the Intellij does not seem to recognize items being brought into context. However, if I write my own version of

context(...)

in the same module it works just fine. Also worth noting that this compiles just fine despite the IDE errors. Is this expected behavior at this point in the release cycle? I'm just eager to start refactoring some of my personal projects to use context parameters!

I updated a project with iOS targets to Kotlin 2.2.0-Beta2. The GitHub action runner images uses Xcode 15.4 (on macOS 14), so I got the compiler error

LockedCameraCapture

is not found (because it requires iOS 18). https://scans.gradle.com/s/kewpe5fwir3ra Is this expected?