A modern programming language that makes developers happier.

kotlinlang

I tracked down my problem from earlier to this: When an actualization of an expected class is a typealias, the compiler generates the Kt class but not the class itself.
Example:
In the multiplatform library:
```// commonMain file Expectations.kt
package foo
expect class SQLException

// jvmMain file SQLException.kt
package foo
actual typealias SQLException = java.sql.Exception```
The -jvm.jar contains SQLExceptionKt.class, but no SQLException.class. In a JVM consumer library, the type foo.SQLException is unknown.

Of course, there's the workaround to always use java.sql.SQLException in the JVM, but if the consumer library wants to implement an interface with @Throws(foo.SQLException::class), it's not possible.

Ah ah, that's how one learn :slightly_smiling_face:

It's not very clear to me how to use it in this specific case after reading the docs, though.