Hey guys :wave: . Are there any plans for SKIE and...
# touchlab-tools
p
Hey guys 👋 . Are there any plans for SKIE and Swift combine? iOS team in my project uses combine everywhere, not asyncSequences. For some reason they do not want to switch to async or use both, so I need to make kotlin flows work with publishers, but I also would like to use SKIE for other benefits 🙂
d
Not working on SKIE, so I can’t share any plans, but I guess it should be possible to build your own bridge between AsyncSequence and Combine, or use KMP-NativeCoroutines which supports Combine. Every team has their own priorities and is working under unique circumstances, but as an iOS dev myself, I would rather reach for the Swift-native async implementation than continuing to build on Combine. Swift Concurrency does not only make writing a couple of classes of bugs impossible due to loads of compiler-level checks. Apple has also not shipped any significant updates to Combine after its initial introduction four years ago, and they’re actively working on removing the dependency of SwiftUI on Combine (see latest observability changes in iOS 17).
p
Thanks for the reply! I used the NativeCoroutines for now, but I will share your message with the iOS team and see how they respond to the combine non-update info. Many thanks 🙂
f
Hi! We currently do not have a plan for supporting Combine (mostly for the reasons Daniel mentioned above. We might reconsider that if there is a sufficient demand for this feature. As with any feature request, you can create a ticket in our repo: https://github.com/touchlab/SKIE/issues For your usecase I would recommend to use KMP-NativeCoroutines and you can still use other features of SKIE - just disable the coroutines interop.
141 Views