wazero

Files

Crypt Keeper 8c2f0928bc Panics caller on exit error (#673 )

This changes the AssemblyScript abort handler and WASI proc_exit
implementation to panic the caller which eventually invoked close.

This ensures no code executes afterwards, For example, LLVM inserts
unreachable instructions after calls to exit.

See https://github.com/emscripten-core/emscripten/issues/12322
See #601

Signed-off-by: Adrian Cole <adrian@tetrate.io>

2022-07-06 16:30:31 +08:00

rust

Panics caller on exit error (#673 )

2022-07-06 16:30:31 +08:00

tinygo

Panics caller on exit error (#673 )

2022-07-06 16:30:31 +08:00

README.md

Adds allocation examples in Rust and TinyGo (#475 )

2022-04-21 18:22:22 +08:00

README.md

Allocation examples

The examples in this directory deal with memory allocation concerns in WebAssembly, e.g. How to pass strings in and out of WebAssembly functions.

$ go run greet.go wazero
wasm >> Hello, wazero!
go >> Hello, wazero!

While the below examples use strings, they are written in a way that would work for binary serialization.

Rust - Calls Wasm built with cargo build --release --target wasm32-unknown-unknown
TinyGo - Calls Wasm built with tinygo build -o X.wasm -scheduler=none --no-debug -target=wasi X.go

Note: Each of the above languages differ in both terms of exports and runtime behavior around allocation, because there is no WebAssembly specification for it. For example, TinyGo exports allocation functions while Rust does not. Also, Rust eagerly collects memory before returning from a Wasm function while TinyGo does not.

We still try to keep the examples as close to the same as possible, and highlight things to be aware of in the respective source and README files.