Ryan Lamansky

If it's still there when .NET 9 releases, I'll integrate it!

> Unreachable code detected I like this. > Property is used instead of type Rider is wrong here. Both the dotnet compiler and Visual Studio correctly resolve the reference. The...

As noted in #59, I don't want to merge the `WebAssembly.` prefixing in the `OpCode` XML due to that being a Rider bug. Any chance you could rebase without those...

That makes sense--I haven't been keeping up with all the add-ons after the original 1.0 spec 😅

Whatever "section type 12" is, it must be a relatively recent addition to the WASM spec. I'll look into this when I have time.

I spent some time on this today and although adding support for the DataCount section is easy, it's only the _first_ problem: your WASM also uses new instructions. Those will...

[My non-web implementation](https://github.com/RyanLamansky/dotnet-webassembly) targets .NET Standard, which is fairly restrictive, though I could make a .NET Classic build that would have full access to the Windows API. If the goal...

One engine's data point: my [.NET-based implementation](https://github.com/RyanLamansky/dotnet-webassembly) inherits all of its limitations from the .NET framework itself, which doesn't seem to have any hard limit on function size (at least...

I gave this some more thought. Although not required by the spec, an advanced WASM-to-native compiler could consolidate duplicate Type entries (if any), and store the run-time type index alongside...

@rossberg-chromium How much better could it be? What `call_indirect` design would allow for fewer operations than read+compare+branch?