import platform.posix.getcwd
import platform.posix.nftw

These are missing in 1.6-RC2. Have they moved somewhere else?

Note I’ve already followed steps detailed in https://kotlinlang.org/docs/install-eap-plugin.html and https://kotlinlang.org/docs/configure-build-for-eap.html

I hope it’s not too late to file issues for Kotlin 1.6.0-RC2. I ran into issues with repeated annotations and what results the compiler APIs return: https://youtrack.jetbrains.com/issue/KT-49651

There's no mention of 1.6.0-* in EAP category of kotlin blog - https://blog.jetbrains.com/kotlin/category/eap/ - overlook?

Is anyone using generateExternals for JS with 1.6.0? I haven't used it in the past due to some minor issues. Now it gives completely non-compilable output, even for some standard JS types(at least for node).

Does the RC2 release support

jvmTarget = "17"

in KotlinCompile?

I am on Intellij Ultimate 2021.3 Beta but my Kotlin compiler is outdated. It is bundled so I can't uninstall and install, how do I get latest one?

I there a maven repository, where I could get 1.6.20-dev-156 kotlin build? I need this fix - https://youtrack.jetbrains.com/issue/KT-50764

https://drive.google.com/uc?id=1nlXWaolgow6_JB-IzfwtbtFqV0oHuY0y Any idea why IDEA isn't detecting the latest EAP plugin?

Hello, I have some questions relating to the new memory manager From the blog post (emphasis mine):

If you have already switched to our new memory manager, which was announced in Kotlin 1.6, you might notice a huge execution time improvement: our benchmarks show 35% improvement on average. Since this EAP release, there is also a concurrent implementation for the sweep phase available for the new memory manager. This should also improve the performance and decrease the duration of garbage collector pauses. Use the 

-Xgc=cms

 flag to enable it for the new Kotlin/Native memory manager.

It looks like we have two memory manager implementations for this release: 1. The block-the-world one, with 35% performance improvement on average 2. The concurrent mark sweep one, not enabled by default, supposed to improve performance, but with no benchmark info What are the reasons that the concurrent mark sweep memory manager, isn't enabled by default? Are there any known issues or remaining drawbacks that motivated the decision for this Kotlin milestone release? Also, are there any reasons you didn't share benchmark results for it?

Hi, I want to test context receivers feature, but IntelliJ says that

The feature "context receivers" is experimental and should be enabled explicitly

, but I can't find anywhere where to activate this ? I have 2021.3.2 with Kotlin 1.6.20-M1 plugin installed via preview channel with a fresh kotlin project with Kotlin 1.6.20-M1 & Java 17 using Gradle 7.4 🤔

Am I missing an obvious way to do something like:

<Context, Return> context(Context) operator fun ((Context) -> (Return)).invoke() = ...

Or is it safe to assume there this will never be possible? ;(

Declaring

kotlin("jvm") version "1.6.20-M1"

seems to break my build:

java.lang.NoClassDefFoundError: com/gradle/scan/plugin/BuildScanExtension
	at org.jetbrains.kotlin.gradle.plugin.KotlinGradleBuildServices$Companion.addListeners(KotlinGradleBuildServices.kt:65)
	at org.jetbrains.kotlin.gradle.plugin.KotlinGradleBuildServices$Companion$registerIfAbsent$1.execute(KotlinGradleBuildServices.kt:57)
	at org.jetbrains.kotlin.gradle.plugin.KotlinGradleBuildServices$Companion$registerIfAbsent$1.execute(KotlinGradleBuildServices.kt:51)
	at org.gradle.api.services.internal.DefaultBuildServicesRegistry.registerIfAbsent(DefaultBuildServicesRegistry.java:115)
...
Caused by: java.lang.ClassNotFoundException: com.gradle.scan.plugin.BuildScanExtension
	... 187 more

Has anyone else had issues updating their MPP project to the 1.6.20-RC? I have a project with a

nativeMain

source set that's used by

linuxX64

etc. After updating, everything builds correctly and all tests pass on every platform, but the

compileNativeMainKotlinMetadata

fails due to unresolved references. It seems like a bug in the new commonizer, but maybe I'm doing something wrong?

Introducing Kotlin 1.7.0-Beta! Try it and share your feedback. • Changes to builder inference • The return of the

min()

and

max()

collection functions • Stabilizing of definitely non-nullable types • Updates for the new Kotlin/Native Memory Manager Read more in the blog post.

Maybe not the right channel for this, but I was using an RC version of the Kotlin compiler and recently upgraded In my project, I now get this error and can't seem to solve it, even if I delete

/build

Compilation failed. Pre-release classes were found in dependencies.
Remove them from the classpath, recompile with a release compiler or use '-Xskip-prerelease-check' to suppress errors
Reason: Class is compiled by a pre-release version of Kotlin and cannot be loaded by this version of the compiler

I've set my Kotlin dependency version to

1.60.0

, has anyone encountered this before? Thank you 😃

Is anyone else getting a ton of IDE errors from 221-1.7.0-Beta? My project is pretty heavy on new features and complicated structures so it's always pretty unstable from the IDE. But it feels extra bad.

Is it possible to try out dev versions, like

1.7.0-release-226

? I’m particularly interested in testing out the fix to this bug https://youtrack.jetbrains.com/issue/KT-52311/javalangVerifyError-Bad-type-on-operand-stack that is present in

1.7.0-RC

. Because

1.7.0-RC2

is not yet released, I would like to test it out

1.7.0-release-226

Not exactly EAP related, but right after I migrated to Kotlin 1.7.0, I am getting this error at runtime. Can someone please help how to resolve this:

internal data class PostmanEnvironment(private val environment: MutableMap<String, String?> = mutableMapOf()) :
  MutableMap<String, String?> by environment {
  fun set(key: String, value: String?) {
    environment[key] = value
  }

  @Suppress("unused")
  fun unset(key: String) {
    environment.remove(key)
  }
}

Error:

Accidental override: The following declarations have the same JVM signature (entrySet()Ljava/util/Set;):
    fun entrySet(): MutableSet<Entry?>? defined in org.revcloud.postman.PostmanEnvironment
    fun entrySet(): MutableSet<MutableMap.MutableEntry<String, String?>> defined in org.revcloud.postman.PostmanEnvironment

Please redirect me if this is not the right channel. Thanks!

Strange maybe error?

val <Key : Any, Value> Mutated<Key, Value>.onEach get(): (suspend Toggled.((suspend Toggled.(Key, Value & Any) -> (Unit))) -> (Unit))

val <Key : Any, Value> Mutable<Key, Value?>.onEach get(): (suspend Toggled.((suspend Togglable.(Key, Value & Any) -> (Unit))) -> (Unit))

If I have these two signatures it calls the top one on Mutated the bottom on Mutable and there is no ambiguity. However if I have these two functions instead:

context(Toggled) @Keyword
suspend fun <Key : Any, Value> Mutable<Key, Value>.onEach(
    block: suspend Togglable.(Key, Value & Any) -> (Unit)
)

context(Toggled) @Keyword
suspend fun <Key : Any, Value> Mutated<Key, Value>.onEach(
    block: suspend Toggled.(Key, Value & Any) -> (Unit)
)

It cannot figure out which one to use. The top one has the same syntax as a result of this function:

context(Toggled) @Keyword
suspend operator fun <Return, First>
    (suspend (Toggled).(First) -> (Return))
    .invoke(first: First)
    = this(this@Toggled, first)

Which used to be a member function of Toggled that I used before context was added.

I'm trying to test an early version of Kotlin 1.7.20,

1.7.20-Beta-54

from the kotlin dev repo of

<http://maven.pkg.jetbrains.space|maven.pkg.jetbrains.space>

. I actually want to test the fix for this issue which should be included in Beta 52+. It actually does fix the issue with the Cocoapods plugin, but my app does not build. The task

linkPodDebugFrameworkIosArm64

fails with

e: Could not find "org.jetbrains.kotlinx:kotlinx-serialization-core" in [/Users/ribesg/Projects/events, /Users/ribesg/.konan/klib, /Users/ribesg/.konan/kotlin-native-prebuilt-macos-aarch64-1.7.20-Beta-54/klib/common, /Users/ribesg/.konan/kotlin-native-prebuilt-macos-aarch64-1.7.20-Beta-54/klib/platform/ios_arm64]

Is it due to it being a beta version or is there some kind of incompatibility introduced with this version that requires an update of

kotlinx.serialization

or something like that? Thanks

🚀 The Kotlin 1.7.20-Beta release is out! • K2 now supports several new plugins • Preview of the ..< operator for open-ended ranges • K/N memory manager enabled by default • Inline classes with generic underlying type (experimental) Try out the new features and report any issues you find to help us improve Kotlin 1.7.20! Learn more in the blog post.

I am seeing “Multiple incompatible variants of org.jetbrains.kotlinkotlin gradle plugin api1.7.20-Beta were selected”. More in thread.

Looks like adding kotlin-generating tasks to KGP is changed/broken in 1.7.20-Beta 🧵 CC @tapchicoma @gavra

Not sure if it has its place here, but it seems to be a bug with 1.7.20-Beta, so I'm writing here. Trying to play with context receivers, I am defining the following function:

fun <C1, C2, R> withBoth(c1: C1, c2: C2, block: context(C1, C2) () -> R): R = block(c1, c2)

And I get this compiler error:

Subtyping relation between context receivers is prohibited

Is this a bug, or did I mess up the syntax somewhere? There is no subtyping intended anywhere here. Note that moving

C2

as a regular receiver fixes the compilation:

fun <C1, C2, R> withBoth(c1: C1, c2: C2, block: context(C1) C2.() -> R): R = block(c1, c2)

How long does JetBrains keep old artifacts:

org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.5.10-release-949

? I want to use

com.jetbrains.intellij.platform:indexing-impl:213.6777.52

which depends on this kotlin version, but this version is not in the cache redirector: https://www.jetbrains.com/intellij-repository/releases/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.5.10-release-949/kotlin-stdlib-jdk8-1.5.10-release-949.pom https://cache-redirector.jetbrains.com/intellij-dependencies/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.5.10-release-949/kotlin-stdlib-jdk8-1.5.10-release-949.pom https://cache-redirector.jetbrains.com/intellij-repository/releases/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.5.10-release-949/kotlin-stdlib-jdk8-1.5.10-release-949.pom

🎉 Kotlin 1.7.20-RC is out! ✅ K2 now supports several new plugins ✅ Preview of the ..< operator for open-ended ranges ✅ K/N memory manager enabled by default ✅ Inline classes with generic underlying type (experimental) Try it and share your feedback! https://github.com/JetBrains/kotlin/releases/tag/v1.7.20-RC

With 1.7.20-RC, I’ve noticed that mockito.argThat no longer seems to work correctly. Trace in thread. I personally don’t feel strongly about this (I don’t expect mockito to work well with Kotlin and don’t really want kotlin to cater to it 😅), just floating for awareness

When upgrading the Kotlin version to 1.7.20-RC from 1.7.10 the following error is thrown on a Gradle sync. How can I figure out what is going wrong here?

Hey I saw today, that there are 1.8.20-dev builds appeared but looks like something gone wrong with versioning, and there is build 3563 for yesterday and 36 for today is it possible to drop 3563 build, so when using

[1.8.20-dev,1.8.20-dev-9999[

version pattern in gradle it will use really up-to-date version? I have a setup in rsocket-kotlin for testing issues with K2 compiler on latest versions, so to understand, if some specific issues fixed or not, and now, it will use all time 3563 version 🙂 for now i’ve changed constraint to up to 3560, but good, that I’ve found it directly now (may be someone also do similar things, who knows)