Dan Gohman

@ibaryshnikov Yes, feel free to file new issues here for discussing design topics. I do think something like `--port` makes sense. We can express blocks of addresses with [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation),...

The original JS polyfill was built from compiling the initial WASI implementation in Wasmtime written in C with Emscripten. Since then, Wasmtime has moved to an implementation written in Rust...

No, there isn't yet a new PR for this unfortunately. A lot of parts of WASI have changed, and are still in the process of actively changing. If you want...

Thanks for putting this together @kubkon! I think it makes sense to merge this, and iterate from here.

On second thought, I agree with @alexcrichton here. There's a lot of boilerplate here, and as WASI evolves, this is going to be more boilerplate that has to be manually...

Can you say more about the motivation for adding `WASM_RT_NO_MEMORY_CHECKS`? A core part of the WebAssembly ecosystem is that the sandbox is always enabled (outside of debugging an implementation or...

A wasm program is running without linear memory sandboxing can read and write to around 8 GiB of host process address space. Depending on the address space layout, this could...

I agree that for the specific use case @kripken describes here where the program is trusted anyway, security is not a concern. And I agree that performance experimentation is cool,...

I appreciate the creativity, but ultimately, checking whether `MEMCHECK` is already defined would still be setting up an extension point for the purpose of letting downstream dependencies alter wasm spec...

The 15K native case with gcc is presumably using dynamic linking, so it doesn't include the C++ standard library. You can see the effect of static linking by compiling with...