Ben Smith
Ben Smith
It probably won't work in ValidateModule, since that would require you to read the data into IR first. I think the way that fits best with the current design would...
Maybe not by default, but I think it makes sense as a flag.
Good point, this should be clarified. But to answer your question, the executables don't depend on anything else, so you should be able to unpack them anywhere convenient. The `.wasm`...
We could do that, but I don't think we have a separate release builder. I guess it could be a different configuration though?
Good catch! This also needs some read_test.cc fixes, which are a bit clumsy to resolve, unfortunately. Here's the patch that I made locally that fixes those issues: [read_test.zip](https://github.com/WebAssembly/wasp/files/9842868/read_test.zip)
I think this is working, but CI is blowing up for a different reason.
Sorry, the WebAssembly text format is a bit confusing. `.wast` is meant to be only for the [WebAssembly spec test script format](https://github.com/WebAssembly/spec/blob/master/interpreter/README.md#s-expression-syntax). This can include multiple modules, as well as...
My guess is that these are outdated, but I think @sbc100 and @keithw will have more information.
The executables are written into the subdirectories, e.g. ~/wasp/build/src/tools/wasp
I think I see what you're getting at @redradist, but the browser already has a specified API, using WebIDL. WebAssembly doesn't need to create its own, it needs a way...