Hey all, I’m running into some issues with object ...

# kotlin-native

[Luke Kellett]

Hey all, I’m running into some issues with object concurrency using Kotin Native 1.3.61. I’m creating an instance of the following class in the UI thread and then calling it’s properties/members from “_DispatchQueue.global(qos: .background).async_” on iOS. It’s throwing kotlin.native.IncorrectDereferenceException even though I’m attributing my variables with @SharedImmutable.

Any ideas?

class ThreadSafetyTest {

    @SharedImmutable
    val mapper: (value: String) -> String = { value: String ->
        "Mapped: $value"
    }

    @SharedImmutable
    val mapper2 = "Mapper 2"

}

[Kris Wong]

@SharedImmutable does not work in that way

[Dominaezzz]

I'm fairly certain @SharedImmutable doesn't work on member.s

[Dominaezzz]

What he said. 😅

[Kris Wong]

i am surprised it's not giving you an error

[Luke Kellett]

Hmmm…

[Kris Wong]

you need to freeze the object

[Luke Kellett]

So what does it work on then?

[Kris Wong]

globals

[Luke Kellett]

Funny that. The freeze() method is unavailable for some reason.

[Dominaezzz]

Are you in common code?

[Kris Wong]

yeah it's a native API, but easy to create expect/actuals for

[Luke Kellett]

commonMain

[Kris Wong]

i'm not sure why JB hasn't put the API in common

[Kris Wong]

everyone targeting native ends up doing it for the most part

[Luke Kellett]

Ohh, so it IS available in say iosMain?

[Kris Wong]

yes

[Luke Kellett]

💣

[Luke Kellett]

Awesome… Thanks!

[Luke Kellett]

FWIW guys… I think the reason freeze() is not available in common is not all platforms have/need it. It looks like Android code for instance doesn’t have the method. I’m guessing the Kotlin Native code is compiled directly into Java bytecode much like it would be as if it was a part of the Android project code.

[Kris Wong]

kotlin/native code is compiled to a native binary

[Kris Wong]

and the fact that it's not used by all platforms doesn't mean it's not needed