Variant 'iosArm64ApiElements-published' capability io.ktor:ktor-client-cio:1.6.0 declares a usage of 'kotlin-api' of a component, as well as attribute '.type' with value 'native': Incompatible because this component declares a usage of 'kotlin-metadata' of a component, as well as attribute '.target' with value 'ios_arm32' and the consumer needed a usage of 'kotlin-api' of a component, as well as attribute '.target' with value 'mingw_圆4' Variant 'iosArm32MetadataElements-published' capability io.ktor:ktor-client-cio:1.6.0 declares a component, as well as attribute '.type' with value 'native': Incompatible because this component declares a component, as well as attribute '.target' with value 'ios_arm32' and the consumer needed a component, as well as attribute '.target' with value 'mingw_圆4' Variant 'iosArm32ApiElements-published' capability io.ktor:ktor-client-cio:1.6.0 declares a usage of 'kotlin-api' of a component, as well as attribute '.type' with value 'native': Doesn't say anything about .target (required 'mingw_圆4') Incompatible because this component declares a component, as well as attribute '.type' with value 'common' and the consumer needed a component, as well as attribute '.type' with value 'native' Variant 'commonMainMetadataElements' capability io.ktor:ktor-client-cio:1.6.0 declares a usage of 'kotlin-api' of a component: The consumer was configured to find a usage of 'kotlin-api' of a component, as well as attribute '.type' with value 'native', attribute '.target' with value 'mingw_圆4' but: > No matching variant of io.ktor:ktor-client-cio:1.6.0 was found. > Could not resolve io.ktor:ktor-client-cio:1.6.0. > Could not resolve all files for configuration ':mingwX64CompileKlibraries'. Resources.srcDir('src/nativeMain/resources')Įxecution failed for task ':compileKotlinMingwX64'. Implementation('io.ktor:ktor-client-cio:$ktorVersion')

Implementation('io.ktor:ktor-client-core:$ktorVersion') Val hostOs = System.getProperty('os.name')Īttribute(OPERATING_SYSTEM_ATTRIBUTE, objects.named(osName))Īttribute(ARCHITECTURE_ATTRIBUTE, objects.named(X86_64)) ThrowInvalidMutabilityException(/Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/native/concurrent/Internal.kt:109)Īt #(/Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/native/internal/Ref.kt:12) : mutation attempt of frozen mutation attempt of frozen kotlin.Throwable#(/Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/Throwable.kt:24)Īt kotlin.Exception#(/Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/Exceptions.kt:23)Īt kotlin.RuntimeException#(/Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/Exceptions.kt:34)Īt #(/Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/native/concurrent/Freezing.kt:24)Īt. at /Users/teamcity1/teamcity_work/6326934d18cfe24e/kotlin/kotlin-native/runtime/src/main/kotlin/kotlin/Throwable.kt:24 We believe that an intention to make an interface applicable for SAM conversion should be explicit.***. FAILED Unlike Java, Kotlin will not allow a SAM conversion for every interface with one single abstract method. It turned out, however, that function types and typealiases don’t cover all the use-cases, and people often had to keep an interface in Java only to get a SAM-conversion for it. The initial idea behind this design was to use function types explicitly for such use-cases. SAM conversions currently only work for Java interfaces and abstract classes. Then the compiler automatically converts the lambda to an instance of the class implementing the abstract member function. SAM conversion applies if you pass a lambda as an argument when an interface or a class with only one single abstract method is expected as a parameter. The community has requested us to introduce support for SAM conversions for Kotlin classes ( KT-7770). Kotlin 1.4 that is going to arrive in spring 2020 will make another step forward for the Kotlin ecosystem. Multiple case studies from companies well-known in the industry show that we are making good progress in this direction. To accomplish this, we’re going to make it shine on all platforms.

Our vision is for Kotlin to be a reliable companion for all your endeavors, a default language choice for your tasks.

During the keynote at KotlinConf, Andrey highlighted our strategic view on the current areas of focus for the evolution of Kotlin, and our plans for Kotlin 1.4 which will be released some time next year.

.klib fike