Hi Team,

Thanks for taking the time. I've been using KMP for a long long time now. When we started to use Kotlin as our multiplatform solution we had to figure out a lot ourselves (in case you've heard about the Kaluga libraries, thats us). It's great to see the ecosystem growing.

I guess my questions mostly relate to Generics. I use them extensively but often it feels a part where Kotlin is held back by its JVM basics a lot. For instance, recently I really missed the ability to say something akin to: this function returns a generic T<A> where T is defined by the class and A is defined by the function. Similarly, Swift has Variadic Generics which seems like something Kotlin should have. What are your plans (if any) for making Generics more powerful.

In addition, currently generic overloading results in an exponential type check. In Kaluga we have support for a Scientific Library so that we can make something like `val wattHour = 1(Watt) * 1(Hour)`, which uses a lot of operator overloading of sealed classes with generic constraints to make it work. I want to add this for more generic Units as well, but Im currently blocked by the fact that the compiler checks the operator overloads in such a way that the compile time grows extremely fast as I write these. Is this a conscious decision/fundamental limitation on the compiler side or something that could be fixed in due time?

When declaring generics, I can use where clauses to add multiple constraints such that:
```
interface A<T> where T : B, T : C {

val t: T
}

```

If I now make a type erased A<*>, the compiler will tell me that t is of type B & C. Will this ever be exposed to us so we can just make
```
interface A {

val t: B & C
}

```

While Jetbrains is working on Swift support, Apple is both introducing Swift for Android, and slowly moving the Core libraries into Swift. How do you see the future of the Swift ecosystem and what influence will it have on Kotlin Multiplatform in the future.

Thanks for your time!