News for hackers. Stuff that matters.
Re:WebAssembly Specification Prototype by icefox on Wednesday July 13, 2016 @03:40PM (#12089045)
It looks like Wasm.instantiateModule(b, m) currently takes the binary wasm and memory to create a module, when would you pass in a linear memory object? Does converting a wast always produce two files?
Re:WebAssembly Specification Prototype by sunfish on Wednesday July 13, 2016 @05:02PM (#12089637)
WebAssembly modules can still import an external linear address space, but they can now also define their own linear address space, with their own initialization data included in the module file.
Re:WebAssembly Specification Prototype by icefox on Thursday July 14, 2016 @09:34AM (#12093578)
So if I understand that correctly unlike the current text ast format that is floating around the Binary Format doesn't include the contents of (memory ...)? So foo.wasm + foo.mem = foo.wast?
Re:WebAssembly Specification Prototype by sunfish on Thursday July 14, 2016 @11:28AM (#12094649)
wasm modules can include their own initializers now, so .mem files won't be needed. This is the Data Section in the WebAssembly docs.

.wast is actually just a testing file format that's currently serving the purpose of a text format in the absence of a real one. It isn't expected to be part of typical user workflows.