Rick Clephas
Rick Clephas
When the current compiler plugin was created KSP didn't support Kotlin/Native and a custom compiler plugin would allow us to modify classes instead of creating extension functions (which seemed a...
> I’d love to be able to suppress those functions being generated, actually. They just wind up being extra bloat on the API surface (the compiler-generated ones) https://kotlinlang.slack.com/archives/C3PQML5NU/p1651707619396539?thread_ts=1651700593.235969&cid=C3PQML5NU
Currently the whole library is focused on Kotlin to Swift cases but there are also valid cases for Swift to Kotlin support. For example you should be able to call...
- Throw `CancellationError`s instead of `KotlinCancellationException`s - Apply back pressure to the Flow collection ### Breaking changes - `asyncFunction(for:)`, `asyncResult(for:)` and `asyncSequence(for:)` throw a `CancellationError` instead of a `KotlinCancellationException` -...
Fixes #29
JS and native share some limitations with the coroutines interop. The generic way of exposing callbacks could be applied to JS as well. Allowing the clients to decide on an...
- Support NSErrors coming from Swift/ObjC - Support something similar to `@Throws`
Relates to [KT-42297](https://youtrack.jetbrains.com/issue/KT-42297). The Kotlin ObjC/Swift is pretty great, but at the moment there are also some gaps (especially with the Swift interop) like suspend functions and enum classes. With...
At the moment gradle plugin boolean properties aren't strictly parsed, meaning that invalid values are interpreted as `false`. Even `true ` is silently ignored and interpreted as `false`. Using `toBooleanStrict`...