Ryan Lamansky

I'll definitely leverage any intrinsics shipped! I'm still concerned about how I'm going to deal with further out features like [atomic memory instructions](https://github.com/WebAssembly/threads/blob/master/document/core/syntax/instructions.rst#atomic-memory-instructions)...

Anyway, back on topic, adding extensibility to make AoT compilation easier to achieve is now on the Potential Future Features list. I looked over all the work you (@mccoyp @lambdageek)...

It should work on any platform that supports `System.Reflection.Emit`. This means no iOS, but you should be okay on other mainstream platforms. I haven't heard of anyone trying it yet,...

If I'm mapping that offset of that exception correctly, it's dying on `DefineDynamicAssembly`, which is the sort of place one might expect to see a `PlatformNotSupportedException`. The alternative solution behind...

I'm mostly waiting on this: https://github.com/dotnet/corefx/issues/4491 When that's done, .NET Core (and maybe even .NET Standard) will have a built-in mechanism to create DLLs. Then this library could be part...

Change `AssemblyBuilderAccess.RunAndCollect` to `AssemblyBuilderAccess.Save`. Other changes will be needed but this will get you past this blocker.

There's probably a missing step at the very end where it actually finalizes all the generated objects into the DLL. I know the process works because what you're doing, I...

@Suchiman Interesting. What kind of changes are required to target reference assemblies?

WASM is fundamentally simple. It doesn't (yet) intrinsically support objects at all, for one thing, and it only has 4 types (int32/64, float32/64). So, any dependencies it takes on the...

> That's surprising! Does that mean pointers are represented as int32/64? The 1.0 spec of WebAssembly's memory is accessed using unsigned 32-bit offsets from a base of 0. This gives...