With initial versions of Swift Export not supporti...

# swift-export

[John O'Reilly]

With initial versions of Swift Export not supporting concurrency interop will it be possible to continue using likes of SKIE alongside Swift Export in the meantime?

[Javier]

Does SKIE work at the same time Swift Export? As Swift Export does not generate any single objective C code I was expecting it to not work

[Javier]

IMO the initial release of Swift Export should include coroutines support, it is too core to ignore it.

[rkechols]

I agree that coroutines are super essential, but there may still be some use cases out there that benefit from swift export even without coroutines. For those I'd say "better sooner rather than later". Coroutines can simply be added first thing after the initial minimal release.

[Anonymike]

Just sharing perspective from my team for a sense of how we view it. We've been monitoring swift export for a while and are excited to see it taking shape! Kudos to the team for the work on it as working in objective-c blows to say the least.

The challenge with coroutines and swift export is many of us have already had to work around not having it. Its not pretty by any means, but we'll probably stick with existing methods until coroutines are supported and wait patiently. Unfortunately the vast majority of our use cases require some form of io be that networking, messaging, long processes, what have you so we can't architect for computation oriented only functionality as that would be too small to justify adding another element without replacing one.

[Artem Olkov]

Hello there 🙂

will it be possible to continue using likes of SKIE alongside Swift Export in the meantime?

No, Swift Export is built entirely on a new stack and is not interoperable with current 3rd party solutions for enhancing Objective-C interop.

It is, in theory, possible to modify KMP-NativeCoroutines to work with swift export. But I'm not sure that's a reasonable task, given the fact that we are working on supporting coroutines right now.

[Artem Olkov]

I would like to draw attention to the fact that, although 2.2.20 does include the initial release of Swift Export, it is designated as experimental. As I stated at the KotlinConf, we do not currently promote production usage. We encourage users to test it out and report bugs, issues, etc. We have already gathered three distinct bug reports that show instances that we overlooked during our internal testing, despite the fact that it is only 2.2.20-RC. With the help of those reports, we can refine our product and make sure Swift Export is ready for production much sooner. Bravo to everyone who reports bugs!

As a team, we are fully aware of how crucial coroutine support is. We are also aware that we cannot replicate every scenario of usage in-house, and we want our users to test our solutions as soon as possible. Otherwise, we'll be releasing more features that users can't use on their computers - and nobody wants that.