ubuntudroid
09/14/2023, 8:02 AMOne real difference between other Coroutines interop solutions and SKIE is that SKIE does not throw exceptions from the underlyingIn our project we already have result object wrappers with error states (we are using [Resultat](https://github.com/nicolashaan/resultat) for that), so we should be fine. But more generally: why change the Flow exception propagation behavior compared to how it would work if the Flow was consumed from Kotlin code, thereby introducing additional stuff to keep in the back of one’s mind when developing shared module code? Is there some technical reason? And if not, why not make this configurable? Would this introduce a lot of complexity in the code generation?. Your Kotlin code will need to deal with exceptions appropriately in its logic rather than expecting that to throw to Swift. Philosophically, this is how we (Touchlab) generally view error handling and KMP. If you’re expecting an error, catch it and make error states an explicit part of the API rather than just letting them bubble up to Swift. However, other developers may not prefer that approach.Flow
Filip Dolník
09/14/2023, 11:16 AMubuntudroid
09/14/2023, 12:38 PMubuntudroid
09/14/2023, 12:49 PMTadeas Kriz
09/14/2023, 7:47 PM