Add WebAssembly target

[igoriakovlev]

Same implementation as in K/JS but without @JsName annotations

[mvicsokolova]

Could you please also elaborate on the publication process of wasm artifacts?

For now, Deploy build has always been red, as wasm target was published from the separate branch. Is the configuration going to be fixed?

[mvicsokolova]

Can we also set up a test build of coroutines with the enabled wasm target and atomicfu dependency before merging this, so that we are sure that no transformations are applied, all dependencies are present and all the necessary artefacts are published?

[igoriakovlev]

Could you please also elaborate on the publication process of wasm artifacts?

For now, Deploy build has always been red, as wasm target was published from the separate branch. Is the configuration going to be fixed?

This tests already runs perfectly with your main teamcity configuration. We are going remove that red wasm configuration as soon as this MR will be merged.

[igoriakovlev]

Can we also set up a test build of coroutines with the enabled wasm target and atomicfu dependency before merging this, so that we are sure that no transformations are applied, all dependencies are present and all the necessary artefacts are published?

I do not know how to do that. I have already made MR for coroutines and this coroutines branch works perfectly with this Wasm AtomicFU on local machine (using train build). But I dont know how to use this train mode on CI.

[mvicsokolova]

Could you please add a test project for atomicfu-gradle-plugin, simillar to this JS project test: https://github.com/Kotlin/kotlinx-atomicfu/blob/3a3deb61243d69740fbded19f02472873e6942b9/atomicfu-gradle-plugin/src/test/kotlin/kotlinx/atomicfu/plugin/gradle/test/JsProjectTest.kt

• to be sure that when the plugin is applied, no transformations are performed, checking that only compile tasks are present
• to check that atomicfu-wasm dependency is present in both compile and runtime classpath

In overall all the changes look good to me 🙏🏻

[hfhbd]

Do you also have plans to add wasmWasi?

[fzhinkin]

BTW, should we also update the README to mention the new target there?
@mvicsokolova

[mvicsokolova]

Rebased the branch on the latest develop branch with Integration tests

[mvicsokolova]

@hfhbd yes, I've added support of wasmWasi target as well 🙏🏻

[mvicsokolova]

I've introduced wasmJs and wasmWasi targets in integration tests: they check atomicfu-gradle-plugin application to the mpp project with both wasm targets declared.

For wasm targets atomicfu-gradle-plugin does not perform any transformations, just adds the implementation kotlinx-atomicfu dependency.

[mvicsokolova]

Mentioned in README that the library provides support of all platforms including Wasm (since Kotlin 1.9.20)