I have a simple Resource Class defined in my shared module - I usually use it as data types for flows returned from my repositories:

sealed class Resource<out T : Any>(open val data: T? = null) {
    data class Success<out T : Any>(override val data: T) : Resource<T>()
    class Failed<out T : Any>(val msg: String, val cause: Throwable? = null, data: T? = null) : Resource<T>(data)
    class Loading<out T : Any>(data: T? = null) : Resource<T>(data)
}

I also have a mapper function with allows mapping the data type to something else:

fun <T : Any, R : Any> Resource<T>.map(mapper: (T) -> R): Resource<R> = ...

This works great on the Kotlin end of things. But I’m loosing all generic information on the Swift end in the mapper function. It seems to just be converted to

(Any) -> Any

which means I need to constantly cast to get what I want which makes the code look really ugly. I read through the official docs and understand, that this is expected. But is there a better way to handle generic and/or generic resources to make them more Swift compatible?

https://github.com/icerockdev/moko-kswift This should help

@Shubham Singh interesting, will check it out, thanks!

Or alternatively put the generic on a class (method object) to avoid losing the type info.

@bnvinay92 I’m not super proficient with Swift, how would that look like?

I meant from the kotlin side of things.

class Mapper<R>(mapper: (MyClass) -> R)

with

fun map(myClass: MyClass): R

oh, got you - yeah, that would indeed lead to quite a bit of ceremony when attempting to chain (which exactly is one of the use cases for me unfortunately).

If you want to chain mappers just map once using kotlin and then convert to a swift type and use whatever is idiomatic in swift

yeah, that would work, and I’ll probably do just that if I don’t find a better solution. Guess I should timebox now. 😅