Ingvar Stepanyan

Maybe I rushed with "comprehensive" bit; looking through the suite, it doesn't seem to test most of filesystem operations, for example, or randomness, or timers. https://github.com/devsnek/node-wasi/tree/master/test/c by @devsnek, referenced from...

Sounds like merging Node & Deno tests and precompiling to WAT alongside existing C files would be a good start then. @devsnek & @caspervonb do you want to uh talk...

> Don't forget the wasi-sdk tests ([WebAssembly/wasi-sdk:tests@`master`](https://github.com/WebAssembly/wasi-sdk/tree/master/tests?rgh-link-date=2020-06-29T19%3A37%3A32Z)).. (i've not looked at how they compare to the node or deno tests but just wanted to make sure they don't get fogotten)....

> Personally I would rather see the testsuite written in C, since the syscall API being tested is so low level. FWIW Rust is equally low-level as a language, and...

@devsnek Yeah, that's basically what I meant (note that you'll need `unsafe` on `main` though for FFI bindings). I think we can even use [`wasi`](https://crates.io/crates/wasi) crate which already provides autogenerated...

> I actually think it would probably make sense to just start by adding the DWARF description to a doc in [WebAssembly/tool-conventions](https://github.com/WebAssembly/tool-conventions/) We sort of did that by linking to...

> Currently I don't know of any other toolchain besides LLVM that generates DWARF like this. FWIW (not that it contradicts your statement) Golang tried that too, but ran into...

Ok so I need to raise issues on proposal repos separately?

Done. Meanwhile, is it worth pushing the partial update here (without tests from those repos) or better to wait until we have no conflicts?

Yes, I'm asking about the script output. I'll submit in a sec.