Why there are so many native targets that are mising coroutines-core artefacts? e.g. all linux targets except x64, watchosX64, mingwX86 & androidNdk

AFAIK: there is no real test infrastructure for automated tests for those targets, and no resources as for now to setup it

Yes, though it's becoming a bit "contradictory" now that @elizarov is also leading Kotlin, which is supporting these platforms and has sufficient infrastructure to test Kotlin on them.

We are working on clarifying our level of support for various targets. We cannot support all of them at the same level. Some of them are more mature and well supported (with libraries, testing infrastructure, etc), others are just experimental without much support behind them.

I'd be happy with untested experimental artefacts for those targets short term

@elizarov If watchosX64 is experimental without much support behind it, it shouldn't be part of the default watchos() shortcut

I think watchosX86 was part of kotlinx.coroutines at some point, back in 1.3.6X, I recall making a live-demo of coroutines running on the WatchOS simulator at Kotlin Day London in 2019 (worked perfectly), so I don't see why watchosX64 would not work.

It's in coroutines but not in ktor 😕

Then, wrong channel?

I saw that statement.

It is still a bit of mess on our side

We are working on clarifying our level of support for various targets. We cannot support all of them at the same level. Some of them are more mature and well supported (with libraries, testing infrastructure, etc), others are just experimental without much support behind them.

As a bit wider