Nick Fitzgerald

> I pass the cargo test -p wasmtime-fuzzing Did you rebase on top of the `main` branch? Because I wouldn't expect the current iteration of code to pass the tests...

They don't influence control for now, but when we get around to implementing the Wasm exceptions proposal, then they will.

> From that perspective, it might even make sense to just add `MemFlags` to the `bitcast` operation ... This makes sense to me. > However, the one place this breaks...

git command line is also higher level and less footgun-y than libgit2

@jgravelle-google, thanks for writing this up. I'd like to reiterate my sentiment from our last video meeting: * that I am in favor of this idea in general and think...

Great proposal and write up, thanks for laying out the motivation so clearly.

> giving the callee a permanent window into the caller's linear memory, Views and `ArrayBuffer`s are already detachable -- perhaps we can reuse this mechanism to avoid making the views...

Ok so just to be 100% clear: in `list-to-memory f`, `f` is called just once and maps a byte length to a pointer (possibly pre-allocated, possibly malloced) where the bytes...

> what if we drop the `wasm`/`end` from the text format, and use it as an escaping for the binary format only. Yeah for sure -- the text format is...

It seems like a reasonable balance that also allows for incremental progress would be * no canonicalization in interface types itself * for the canonical ABI and JS, interface type...