Kotlin/JS dynamic type used for interoperability with untyped or loosely typed objects is not supported yet. Workarounds for Kotlin/JS features non-supported in Kotlin/Wasm Dynamic type If you try to use JavaScript try-catch expression to catch the Kotlin/Wasm exceptions, it'll look like a generic WebAssembly.Exception without directly accessible messages and data. The Kotlin/Wasm try-catch expression can't catch the JavaScript exceptions.

Type Any will be deprecated in Kotlin 1.9.0. This includes arrays, Throwable class, collections, and so on. Type Any will be deprecated in Kotlin 1.9.0 in favor of the JsHandle class Opaque object for Kotlin types JS value for external types In Kotlin, the type system distinguishes between references that can hold null (nullable references) and those that can not (non-null references). From Kotlins documentation about null-safety.

Parameters and return values of function types follow the same type of conversion rules. 2 Answers Sorted by: 3 Your problem is that youre using nullable Strings when attempting to implement the interface. Only when non-nullable and in functions returning position.įunction type, for example ( int, String) → Int In the future, the stringref proposal could allow the zero-copy string interop.

Kotlin default visibility modifier