Hey, I have updated my Kotlin/Wasm samples with Ko...

# webassembly

[sdeleuze]

Hey, I have updated my Kotlin/Wasm samples with Kotlin 1.8.0-RC2 https://github.com/vmware-wasmstack/wasm-languages/commit/5307fce22efd8354451056281d96515fa55f1b3b. Looks like it now works fine with Chrome stable (108) using the --js-flags=--experimental-wasm-gc flag.

Looks like support on Google Chrome unstable (110) is broken, I get the following error:

async module:63 Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(): Compiling function #14:"kotlin.collections.IteratorImpl.hasNext" failed: call_ref[0] expected type (ref null 72), found struct.get of type (ref null 2) @+12373
await (async)
m.a @ async module:49
475 @ wasm-example.js:1
m @ bootstrap:19
(anonymous) @ startup:4
(anonymous) @ wasm-example.js:1
(anonymous) @ universalModuleDefinition:9
(anonymous) @ universalModuleDefinition:1

I guess that's expected, but just wanted to check with the Kotlin/Wasm team.

Also, I was not able to find how to enable permanently Wasm GC flag as shared by @bashor on https://twitter.com/bashorov/status/1603539987538010113 in my installation of Chrome unstable (110), the entry is not available, not sure why.

[Svyatoslav Kuzmich [JB]]

1.8.0-RC2 is already behind supported V8 version in the latest chrome.
1.8.20-dev-4608 should work.

Also, I was not able to find how to enable permanently Wasm GC flag

🤷 I do have this option in 111.0.5483.0 (Official Build) canary (arm64) on a Mac.

[sdeleuze]

Ok I just need to wait for Chrome 111 to be available on Archlinux then.

[bashor]

I guess your Chrome unstable == Dev channel (Chrome Release Channels).

[sdeleuze]

Let me check

[bashor]

I have a flag in the current Dev version on macOS 110.0.5481.24

[sdeleuze]

I think I tried and 1.8.20 snapshots works fine with Chrome 110

[sdeleuze]

GC evolved (again ^^)