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?

📣We’ve made changes to how release information is organised in Kotlin YouTrack: the "Target versions" field has been replaced by two new fields: "Planned For" and "Available In". • The "Planned For" field indicates the upcoming release version in which the reported issue is planned to be resolved. • The "Available In" field is updated automatically once the issue is fixed, showing the release version(s) where the relevant changes have been or will be delivered. You’ll always know which release version to expect a fix in ("Planned For") and can quickly find out in which versions changes have already been made available ("Available In"). kodee excitedThank you for your attention and for continuing to share your feedback with us! 💡

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

Hello 👋 I got this warning on Kotlin 2.2.0-RC, is there a specific diagnostic ID to suppress it? We enabled

allWarningsAsErrors

so it becomes a problem if we cannot suppress this particular warning 😬

w: Experimental context receivers are superseded by context parameters.
Replace the '-Xcontext-receivers' compiler argument with '-Xcontext-parameters' and migrate to the new syntax.

I tried with this but doesn't seem working

freeCompilerArgs.add("-Xwarning-level=CONTEXT_RECEIVERS_DEPRECATED:disabled")

Hi. Does Kotlin Bootstrap repo require auth now?

@Kirill Rakhman has left the channel

@Stanislav Ruban has left the channel

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

kodee greetings* Kotlin 2.2.0-RC3* has been released!

K Kotlin 2.2.0 has been released! For more details, please refer to What’s new. kodee frustrated We're improving our Kotlin documentation for new releases and we need your input! Please help us by completing a 10-minute unmoderated usability session, where you'll explore some of our docs while we record your screen and voice (with your consent, of course). Interested? Start by taking this short survey to check if you’re eligible for the study.

kodee walking Kotlin 2.2.20-Beta1 has been released! For more details, please refer to What’s new: https://kotlinlang.org/docs/whatsnew-eap.html.

maybe a dummy question but how fast is KSP usually to publish a version compatible with a Kotlin EAP? I'd like to test my project, but it relies on KSP

Hi.... 🙂

i am a indian.

i like kotlin programming language because of swing, ktor & all new feature. It's a opensource.

kodee welcoming* 2.2.10-RC* has been released.

Hey! kodee naughty Have you trie*d Kotlin’s context parameters?* We’re doing research to learn how developers use them in real projects — and we’d love to hear from you! We’re looking for participants who: • Have already tried context parameters • Are willing to talk about their experience • Can optionally share a small piece of code where they used them The session will involve a conversation about your use cases, what worked well, and what was confusing, plus a look at IDE and documentation experience. 🕒 Duration: 60 minutes 📍 Format: Remote (Google Meet) 🎁 Thank-you gift — you’ll be able to pick one after the session If you’re interested, please book a time that works for you ⚡

Maybe someone is willing to share their experience with context parameters in public here, as well? Has anyone who was brave enough to already use

context receivers

in production code / in larger projects already migrated to

context parameters

? It is already more robust than context receivers? When I added context receivers to my code, there were many problems with byte code errors, e.g. when I combined

context(…)

with lots of other keywords (

suspend

,

inline

etc.). I worked around those cases. Now I’m unsure if I should already try to migrate to context parameters or wait until Kotlin 2.3.

kodee walking Kotlin 2.2.20-Beta2 has been released!

I'm starting to try out Swift Export in a small project here and getting following after switching to using

embedSwiftExportForXcode

.

Showing All Messages
> Task :shared:linkSwiftExportBinaryDebugStaticIosSimulatorArm64

e: Compilation failed: Global 'ktypew:kotlin.collections.List' already exists

I have noticed a problem with composable functions on JS/wasmJS in 2.2.20. I've created a reproducer and opened an issue: https://youtrack.jetbrains.com/issue/KT-80024/JS-WasmJS-IrLinkageError-on-2.2.20-Beta2-RC-when-calling-overriden-composable-function-with-lambda-parameter-from-a-different

kodee happy Kotlin 2.2.20-RC has been released! Read more in What’s new: https://kotlinlang.org/docs/whatsnew-eap.html.

Hello. After 2.2.20-Beta2 and the fix for

<https://youtrack.jetbrains.com/issue/KT-76842>

the project root is added to the static directories served by webpack dev server. While I understand the motivation I'm not sure anyone tried working with a real JS or wasmJS project after this change. Any change to the kotlin sources makes webpack reload the application before the compilation/build is finished. In fact we can see more subsequent reloads, while other files in the project are modified by the compiler and bundler. And very often we end up with a syntax error, when the browser tries to load a broken, unfinished js file. In my opinion this change is a serious mistake. @Ilya Goncharov [JB] @bashor

kodee happy Kotlin 2.2.20-RC2 has been released! Read more in What’s new: https://kotlinlang.org/docs/whatsnew-eap.html.

Hi as its mentioned in docs to test some of experimental features in kotlin 2.2.20, we can add freeCompileArgs and then test them, but i tried adding this :

compilerOptions {
        freeCompilerArgs.add("-Xdata-flow-based-exhaustiveness")
    }

But still not able to test data-flow-based-exhaustiveness, it still shows same old error: Add remaining branches Similarly for adding language version as 2.3.0 in compilerOptions, that also does not apply:

compilerOptions {
    languageVersion.set(org.jetbrains.kotlin.gradle.dsl.KotlinVersion.KOTLIN_2_3)
}

How i can test them?