Hi all. Does anyone here know why `Kotlin.Result<T>` types doesn't get exposed to objective c? I ha...

# ios

[xxfast]

Hi all. Does anyone here know why Kotlin.Result<T> types doesn't get exposed to objective c?

I have a kotlin signature that looks like

fun example(): Result<Unit> = Result.success(Unit)

which gets exposed as

- (id _Nullable)example __attribute__((swift_name("example()")));

in objective-c

[xxfast]

Digging down the slack history, i found this from @Bernd Prünster
https://github.com/a-sit-plus/KmmResult and its cool

but i'm wondering if this is bug/feature is documented anywhere?

[François]

Not a bug, in-line function are not supported

[François]

The alternative way is using kotlin sealed class as enum

[xxfast]

Sorry, where is the inline function? 🤔

[François]

Result itself (... inline class, but same effect)

[xxfast]

ah right - keep forgetting that the Results are inline classes

[xxfast]

thanks

[xxfast]

this is documented here https://github.com/kotlin-hands-on/kotlin-swift-interopedia/blob/main/docs/classesandinterfaces/Inline%20classes.md

[François]

Then you can use the kmmResult lib or sealed class managing the result value.

[François]

https://skie.touchlab.co/features/sealed

[Bernd Prünster]

Just beware that both sealed classes and KmmResult introduce instantiation overhead. On a related note: runCatching will catch errors you don't want to have caught, which is why KmmResult relies on Arrow's nonFatalOrThrow