Shu-yu Guo

Hm, my hunch is that it's kind of hard at the spec level. For the encoding, are you imagining this would require a particular encoding? UTF8, 16? What if the...

Great to hear! I'd still like to figure out why the shell version is 2x faster, though.

Parsing C-style casts are really a pain in the ass. There are a couple of problems with C-style casts: 1. Ambiguity with call expressions. `(e1)(e2)` could be a call or...

> @syg I am personally fine with anything here. --trace-atomics-wait has been useful for me in the past occasionally, and the thing about it is that it’s useful specifically in...

Another option here is to keep the pre-hook needed for `--trace-atomics-wait`, remove the other hooks, as well as the handle. The handle is probably 70% of the complexity I want...

I do, yes, but it's not clear to me when I should be doing that. This PR is phase... 3, I think? How should integration PRs like this land? My...

cc @kripken for thoughts on the design for emscripten-generated code.

> Would it be acceptable for all memories to have a working resizableBuffer attribute added, rather than keying it off a new flag in the memoryDescriptor? Otherwise, there'd be an...

A third path would be another way to signal intent for what kind of buffer you want that's not on the MemoryDescriptor. I'm not fully clued in on the intent...

I feel somewhat strongly that aliasing buffers like that on the JS side is a bad idea. 1. You're right that the buffer aliasing already exists for wasm-manipulated memory, but...