Big Chungus
11/03/2021, 5:23 PMimport platform.posix.getcwd
import platform.posix.nftw
These are missing in 1.6-RC2. Have they moved somewhere else?Matthew Murray
11/09/2021, 2:24 AMralf
11/11/2021, 4:36 AMTomasz Krakowiak
11/11/2021, 5:52 AMTomasz Krakowiak
11/11/2021, 6:29 AMNick Halase
11/12/2021, 4:54 PMjvmTarget = "17"
in KotlinCompile?Gopal S Akshintala
11/16/2021, 10:51 AMTomasz Krakowiak
01/26/2022, 4:49 PMExerosis
02/08/2022, 6:40 PMlouiscad
02/09/2022, 10:24 PMIf 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 theIt 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?flag to enable it for the new Kotlin/Native memory manager.-Xgc=cms
Ayfri
02/09/2022, 11:36 PMThe 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 🤔Exerosis
02/14/2022, 3:54 AM<Context, Return> context(Context) operator fun ((Context) -> (Return)).invoke() = ...
Or is it safe to assume there this will never be possible? ;(rocketraman
03/03/2022, 6:21 PMkotlin("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
AJ Alt
03/25/2022, 5:40 PMnativeMain
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?Alina Dolgikh [JB]
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.Gavin Ray
05/10/2022, 1:46 PM/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 😃Exerosis
05/22/2022, 11:05 PMzak.taccardi
05/31/2022, 12:21 PM1.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
Gopal S Akshintala
06/17/2022, 12:13 PMinternal 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!Exerosis
06/27/2022, 1:35 AMval <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.ribesg
07/19/2022, 2:28 PM1.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?
ThanksKsenia Shneyveys
08/01/2022, 5:16 PMuli
08/03/2022, 9:02 AMZac Sweers
08/03/2022, 8:17 PMJoffrey
08/12/2022, 2:55 PMfun <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)
hfhbd
09/08/2022, 7:40 AMorg.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.pomKsenia Shneyveys
09/08/2022, 6:45 PMZac Sweers
09/08/2022, 7:22 PMThomas
09/09/2022, 12:03 PMOleg Yukhnevich
09/21/2022, 12:10 PM[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)