Keith Winstein

It would be nice to have _something_ like this, because it's pretty challenging to debug a program that's been compiled from, e.g., C++ (via g++) to Wasm (and then, via...

I think we'd be happy to take a PR for this.

I think it would be quite feasible to do **most** of the Wasm C API -- basically all the parts that don't require interpreting Wasm at runtime. It would be...

@marcusb fyi

> Regarding splitting output into multiple C files. I agree that could be a good idea, but I think one file per function might be a little too much. I...

This looks quite interesting! Big-picture questions: - Who is this for / what are some intended use-cases? - Is this helpful for RLBox or Firefox? - Does WASI have any...

On the testsuite, I think anything that gives confidence that the code works as intended (and will be robust to well-meaning but unintentionally buggy refactors) sounds fine to me. Maybe...

That sounds fine to me -- I guess the plan would be that the testsuite first compiles all these .c files to .wasm by using emscripten? If there's a pre-existing...

wasi-sdk is great too, but, where do we pull that in from for the CI tests? (With emscripten I know there's an emsdk:latest Docker repo that wabt already uses...)

Will be fixed by #2021