Hi, since upgrading to

1.3.60

, my iOS application crashes with one of the following assert from memory.cpp: - RuntimeAssert "Must be positive" - RuntimeAssert "cycle collector shall only work with single object containers" Sadly, I am not able to pinpoint or reproduce this issue with sample code. The only stack I have is the GarbageCollector failing. Any hints on what or how to investigate would be much appreciated. More info in the thread.

I'm unable to resolve

kotlin.native.concurrent.freeze()

. Can anyone tell me what gradle imports I need? Cannot find it online...

What’s the best way to debug K/N? I’m using it for #advent-of-code for the first time. I started out by following https://kotlinlang.org/docs/tutorials/native/basic-kotlin-native-app.html and I also installed the “native debugging support” plugin for intellij. But when I try to create a “K/N Application” run configuration I can’t select any of my main functions. Also unlike with kotlin jvm they don’t get highlighted to run. I’m using the latest Intellij Ultimate version (2019.3)

just refreshed my memory on stuff i haven’t looked at since ObjC days.

Int

on iOS is arch dependent and a bunch of articles seem to recommend using

Int

despite that all iPhones and iPads since 2013 and Watches since 2015 are now 64-bit. So….assuming I don’t want to burden API callers with the difference, is there a smart way to pass Swift

Int

down and handle it appropriately in the following case?

let value = 5 // value is of type Int, so platform dependent

print("before: \(value)")
print("after: \(HelloKt.plusplus(value: value))")
// Cannot convert value of type 'Int' to expected argument type 'Int32'

in commonMain:

fun plusplus(value: Int): Int {
    return value + 1
}

fun plusplus(value: Long): Long {
    return value + 1
}

map to

+ (int32_t)plusplusValue__:(int32_t)value __attribute__((swift_name("plusplus(value__:)")));
+ (int64_t)plusplusValue___:(int64_t)value __attribute__((swift_name("plusplus(value___:)")));

respectively in iosMain:

fun plusplus(value: integer_t): integer_t {
    return value + 1
}

fun plusplus(value: NSInteger): NSInteger {
    return value + 1
}

map to

public typealias NSInteger = kotlin.Long // 64 bit signed
public typealias integer_t = <http://kotlin.Int|kotlin.Int> // 32 bit signed

respectively Any ideas?

Is code completion for C libraries broken in the Kotlin 1.3.61 IntelliJ plugin? Using the following in the build.gradle.kts file:

// ...
        compilations.getByName("main") {
            cinterops.create("ncurses") {
                includeDirs("-L${System.getProperty("user.home")}/ncurses-6.1/include")
            }
        }
// ...

Would a symbolic link to a header file break code completion?

What would be idiomatic way to create kotlin objects in iOS app (swift code), that could have mutable structures inside it? E.g. object, that have mutable map. Object will be passed multiple times between swift and kotlin, and will be alive for hours during application execution. Immutable objects are not suitable, as we need to modify up to 100K of such objects per second. Mutability needed only from Kotlin code. Now we use separate thread on Swift side, and we have lot of boilerplate code, to ensure, that all kotlin objects are accessed from single thread only. I'm looking into way to simplify it on swift side, and allow pass these specific kotlin objects across entire app.

The Kotlin Native compiler (Konan) is outputting a boat load of warnings relating to the gtk3 mappings. What do these warnings mean?

Found a memory leak checker that will output issues if any are found. Below is a example:

Memory leaks detected, 1 objects leaked!
Use `Platform.isMemoryLeakCheckerActive = false` to avoid this check.

Please contribute if you are good in big numbers https://github.com/kavanmevada/kotlin-native-bignum

From 1.3.60 release:

Standard CLI library kotlinx.cli is shipped with the compiler distribution (GH-3215)

Does it mean that I could use

kotlinx.cli

without adding any dependency to it?

my iOS tests in one of my projects started SIGSEG'ing for some unknown reason, with no stack trace. has anyone run into this?

Does anyone know why

section

and

row

are vals on

NSIndexPath

? They are vars in Swift, and since they're vals in the native bindings, there's no way to set them.

Is there an easy way to downgrade the K/N compiler?

I updated to 1.3.60 and now it’s saying my module is invalid due to incompatible K/N libraries (they were compiled with 1.3.5x I believe)

What is the best way to load test data from some file for native test? In JVM I would just put it into

res

folder and then use

Classloader#getResourcesAsStream()

, but it is not available in native target.

Has anyone used

kotlinx.coroutines.runBlocking

on iOS? https://github.com/bootstraponline/run_blocking/blob/master/src/commonMain/kotlin/example/Common.kt https://github.com/bootstraponline/run_blocking/blob/master/src/iosMain/kotlin/example/RunBlocking.kt I have a simple example that compiles to an iOS framework. iOS hangs on

kotlinx.coroutines.runBlocking

and never returns. On the JVM, runBlocking works as expected.

The Linux version of Kotlin Native 1.3.60 is missing: https://github.com/JetBrains/kotlin-native/releases/tag/v1.3.60

Some of you (@roamingthings for example 🤗) came to my KotlinConf talk of Kotlin Native running on Rasbperry Pi and thank you for all the feedbacks. Just want to share my slides for those who weren’t there! https://speakerdeck.com/jinqian/native-on-raspberry-pi-62f5c937-9e28-434f-98d2-15e776a0a101

Hello folks, do you know how to enable bitcode on a staticlib?

One of the talks at Kotlinconf mentioned that enums and sealed classes don’t translate well to Swift, and that by using them you lose compile errors when not covering all enum cases with a switch statement etc. One of the suggested solutions was to write Swift enum wrappers for them. I’m curious if there is a ticket for this that I can follow, or some other proposed solution that’s planned?

I would like to export my dependency to the shared lib, so I can use it in C. It is about the bignum lib. Any clue why it is not included in the output? <https://gist.github.com/RdeWilde/5fb125cd3b69d49ea483e8a824f32708> Line 66 should've done the trick, but I don't think it is executed, or at least not included in the output header file. I used this as a reference: <https://github.com/JetBrains/kotlin-native/issues/3571>

Is there a smart way to extend the exported structs? I would like to add a few additional things, like user defined conversion:

auto ionspinlib = libmylib_symbols()-><http://kotlin.root.com|kotlin.root.com>.ionspin;
auto KBigInteger = ionspinlib.kotlin.bignum.integer.BigInteger;

class CBigInteger : libmylib_kref_com_ionspin_kotlin_bignum_integer_BigInteger { // KBigInteger
public:
    CBigInteger(long amount) : KBigInteger.BigInteger(amount) {} // << PROBMLEM
//    {
//        big = KBigInteger.BigInteger(amount);
//    }
    operator long() const { return 10l; }
};

CBigInteger amount = 10l;
long longAmount = amount;

it seems like I can't use the dot-notation in the constructor call

KBigInteger.BigInteger

Hi, Is there any support for kotlin-native on Linux ARM32 soft-float ABI? I tested, and it runs fine on both ARM64 and ARM32 hardfp, but the libraries and OS on the embedded device i'm planning to use it are compiled to ARM32 softfp (specifically ARMv5 EABI). I dug a little on the source code, and based on this file https://github.com/JetBrains/kotlin-native/blob/master/konan/konan.properties there's in fact no support. If there's no support, how would I be able to add it? Thanks!

message has been deleted

Can’t you use

platform

code in the

iosMain

sourceSet that gets generated by adding the

ios()

target? If you can’t, why does it generates it anyway?

Hey All, I am making a multiplatform library. On the iOS side, i was able to selectively perform linkTask using buildTypes parameter in framework (inside target.binaries). But it is still compiling for all targets. How do I selectively compile using build type?

Any reason this is not upvoted? Does this really not cause any problem to anyone? What’s the reason for this? https://youtrack.jetbrains.com/issue/KT-23529

If I try to do a switch in Swift on a KotlinEnum and provide a case for each constant, the compiler gives an error that switch must be exhaustive and it needs a default clause. Is that a limitation of the interop or will it be different in future?