I am piloting 1.9.20-RC and running into some issu...

# kotlin-native

[Jacob Rhoda]

I am piloting 1.9.20-RC and running into some issues. I use the pattern where I expect a type in my common code, and use actual typealias to make it a native type in my platform code. Specifically, I use it to make an iOS/Android library type into a common type. However, wherever I use this type in common code, the compiler is telling me that I need to opt-in with the ExperimentalForeignApi . However, it doesn’t appear that the kotlin.cinterop package is available in common code. How do I work around this?

[mbonnin]

https://youtrack.jetbrains.com/issue/KT-62322/common-declaration-for-ExperimentalForeignApi

[Jacob Rhoda]

It seems like that kind of breaks the whole idea of expect/actual…but maybe I’m missing something of how the code should be structured.

[mbonnin]

I think the idea is that you shouldn't put platform dependent numbers in expect/actual

[mbonnin]

Not 100% sure why, maybe https://youtrack.jetbrains.com/issue/KT-41509/Commonizer-Commonize-numeric-types-with-different-bit-width can help there

[Jacob Rhoda]

Hmm. The thing is that I don’t need to do computation. I just need to an API to pass this value along to the actual implementation. For example, I wrote a wrapper around the AppAuth libraries to provide authentication on both platforms with a common API. They don’t really care the AuthState implementation, it just needs to pass along a reference to the platform code.