Sam Clegg

For the purposes of a logging interface, is the that cost of reading a UTF8 string from an ArrayBuffer in JS really that different from reading a WTF16 string from...

I don't think anybody here is suggesting you are mad. Regarding the first part of your example (that part about the cost of including malloc) wouldn't it make more sense...

Would it make sense to add a region of heap like llvm does for stack data? The convention that llvm uses is a wasm global called `__stack_pointer` which grows down....

(Doing so would also avoid stuff like `const staticBuf = memory.data(256);` which waste memory and won't play nice with threads.)

If we want to take inspiration for existing APIs, it might be worth looking at what linux chose to do: https://man7.org/linux/man-pages/man3/syslog.3.html. We might also want to consider whether we are...

Some parts of this are documented in https://github.com/WebAssembly/WASI/blob/master/design/application-abi.md

It sounds like you are asking about load-time dynamic linking of different wasm modules. That is certainly something that we are hoping to specify one day but we are not...

Actually I just realized to are writing your own compiler so you are probably not going through the static linker at all. In that case you might find this document...

Includes a single-header implementation of a wasm object file streamer: https://github.com/aardappel/lobster/blob/master/dev/src/lobster/wasm_binary_writer.h

I think we should try to stick to tools that are used by WebAssembly core and/or other proposals/subgroups. I would also worry that `mdbook` is quite specific to the rust...