wazero

Files

Crypt Keeper 03bfa31928 Makes all examples and docs use Runtime.Close (#537 )

This removes tedium in our examples and docs by using `Runtime.Close`
instead of tracking everything. Internal tests still track too much, but
anyway at least this stops suggesting others should do it.

This also changes our examples to use log.PanicXX so that the line
number goes into the console output.

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

2022-05-10 12:08:25 +08:00

rust

Makes all examples and docs use Runtime.Close (#537 )

2022-05-10 12:08:25 +08:00

tinygo

Makes all examples and docs use Runtime.Close (#537 )

2022-05-10 12:08:25 +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.