wazero

Files

Crypt Keeper 0d76b11d66 Adds Emscripten integration (#678 )

This adds a toehold integration for emscripten users, so they don't
have to define the memory growth function.

Fixes #601

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

2022-07-18 07:51:48 +08:00

testdata

Adds Emscripten integration (#678 )

2022-07-18 07:51:48 +08:00

.gitignore

Adds allocation examples in Rust and TinyGo (#475 )

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

greet_test.go

Adds allocation examples in Rust and TinyGo (#475 )

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

greet.go

Enable wasm 2.0 support in tinygo examples to allow running with wasm… (#672 )

2022-07-05 15:23:38 +09:00

README.md

Adds allocation examples in Rust and TinyGo (#475 )

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

README.md

TinyGo allocation example

This example shows how to pass strings in and out of a Wasm function defined in TinyGo, built with tinygo build -o greet.wasm -scheduler=none -target=wasi greet.go

Ex.

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

Under the covers, greet.go does a few things of interest:

Uses unsafe.Pointer to change a Go pointer to a numeric type.
Uses reflect.StringHeader to build back a string from a pointer, len pair.
Relies on TinyGo not eagerly freeing pointers returned.

Go does not export allocation functions, but when TinyGo generates WebAssembly, it exports "malloc" and "free", which we use for that purpose. These are not documented, so not necessarily a best practice. See the following issues for updates:

WebAssembly exports for allocation: https://github.com/tinygo-org/tinygo/issues/2788
Memory ownership of TinyGo allocated pointers: https://github.com/tinygo-org/tinygo/issues/2787

Note: While folks here are familiar with TinyGo, wazero isn't a TinyGo project. We hope this gets you started. For next steps, consider reading the TinyGo Using WebAssembly Guide or joining the #TinyGo channel on the Gophers Slack.