Ryan Lamansky

I always thought globals were scoped to the instance, not the thread. This distinction matters for non-JS implementations, where shared-memory threading can be a platform feature that WebAssembly gets for...

Why not leave the current Data section and behaviors as they are, and make a new section for a runtime accessible source?

Some non-web platforms will have it easier. .NET or Java-based WASM implementations, for instance, also have garbage collection readily available. I agree with the GC-free sub-language concept, this provides a...

I was thinking a binary source map format designed for WASM specifically would be more desirable than re-using the JavaScript format. But I'm not a browser vendor so I'm not...

One thing that makes this easier on recent versions of .NET is the [`Span`](https://learn.microsoft.com/en-us/dotnet/api/system.span-1.-ctor?view=net-6.0)) type (and the related ReadOnlySpan). One of the constructors takes a `Void*` parameter, which can be...

Yeah, it's extremely useful and didn't exist when I first started development (this project's first commit is April 2017, `Span` came with .NET Core/Standard 2.1 in May 2018). I've considered...

That would certainly be useful! I don't expect to have time to add this feature any time soon, but contributions are welcome.

Can you link to the spec for these instructions?

Well, the original purpose of the library is simply the outcome of me reading through the WASM spec, realizing how close it was to the .NET CIL spec, and deciding...

@lambdageek My current thought is to modify the compiler to emit instructions more abstractly. The built-in process would still default to wrapping AssemblyBuilder, but it could be swapped out with...