How do you deal with

NSInteger

in common Darwin code? 😮

You have both 32 and 64 bits targets?

Yes

Then, it doesn't work yet unfortunately

😅

I dealt with it by not using commonizer but hacking deep instead.

Maybe I can add

Int.toNSInteger()

and

NSInteger.toInt()

extensions in each target with actual/expect?

You can try, I'm curious if it'd work.

Yeah depends on the use case, just like

.toInt()

vs

.toLong()

.

0

is always good 🙂

Because watchOS is weird IIRC

Yes

Cool that it works, that's an interesting workaround if you can limit that to a small amount of code

Yeah and you could probably also share this as a reusable library

I think I'm going to use that hack in #splitties as well

🤷‍♂️ would be nice

Relevant issue https://youtrack.jetbrains.com/issue/KT-39324

I don’t think that will help here. You can commonize in multiple dimensions, for example: arm64 <- ios-arm64 & macos-arm64 & tvos-arm64 ios <- ios-arm32 & ios-arm64 & ios-x64 But you likely cannot mix those approaches. Commonizing by platform makes more sense than by architecture. But that means we still don’t know the size of

NSInteger

in that commonized code.

In Swift NSInteger is 32 or 64 bit depending on architecture. We once had crashes on 32 bit devices because of it because of common Swift code. We switched to Int32/Int64. So Kotlin can handle it in the same way as Swift does and maybe recommend specific sized ints.

@Jurriaan Mous Aren't Swift's

Int

actually

NSInteger

s?

It would be rather unexpected if Kotlin’s

Int

randomly switches from 32 to 64 bit like Swift’s

Int

🤔

Since

NSInteger

is just a typealias to

Int

or

Long

, you can sometimes get away with using

convert()

to avoid platform-specific expect/actual. https://kotlinlang.org/api/latest/jvm/stdlib/kotlinx.cinterop/convert.html

Int32 and Int64 I meant. Too much Kotlin lately so I misremembered. I would let Kotlin work as Kotlin so let Int be 32 bit. Only talking about NSInteger.

Yes, Kotlin could make

NSInteger

and

NSUInteger

proper integer types and povide all the conversions and operations on its own.

@Marc Knaup Basically, all watchOS targets have Swift's

Int

(aka.

NSInteger

) resolve to a 32 bit integer (aka. Kotlin's

Int

), right?

@louiscad that's how I understand it. I haven't tested that though.

Yes that is the case. I have this build logic in Multiplatform Settings to handle it because I need some

NSInteger

-based expect/actuals https://github.com/russhwolf/multiplatform-settings/blob/master/buildSrc/src/main/kotlin/BuildHelpers.kt#L138-L151