WasmGC is a prototype that only supports the bare minimum that is enough for languages with high level constructs only but not for something like C# which has i

WasmGC is a prototype that only supports the bare minimum that is enough for languages with high level constructs only but not for something like C# which has interior object pointers (ref) and uses them heavily for performance (spans are built on top of them). The API of WasmGC is really rudimentary. With that said, you can track support of various WASM features by .NET here: https://github.com/dotnet/runtime/issues/94351 https://github.com/dotnet/runtime/issues/94351 I don’t understand how the logic of your post works however, WASM in .NET is already used in production versus something that is an early alpha? Also, on Kotlin and targeting something that is not Android - “Java Interop” that’s all I need to say.