25493fe271
Before, our README said gojs `GOOS=js compiled wasm` was experimental. However, as we head to 1.0 we should be more explicit about that. When we started gojs, there was no likely future where `GOOS=wasi` would happen in the standard go compiler. This has changed, so we'll only keep the gojs package around until wasi is usable for two Go releases. Being in an experimental package helps others know to watch out for this. Signed-off-by: Adrian Cole <adrian@tetrate.io>
Import go func example
This example shows how to define, import and call a Go-defined function from a WebAssembly-defined function.
If the current year is 2022, and we give the argument 2000, age-calculator.go should output 22.
$ go run age-calculator.go 2000
println >> 21
log_i32 >> 21
Background
WebAssembly has neither a mechanism to get the current year, nor one to print to the console, so we define these in Go. Similar to Go, WebAssembly functions are namespaced, into modules instead of packages. Just like Go, only exported functions can be imported into another module. What you'll learn in age-calculator.go, is how to export functions using HostModuleBuilder and how a WebAssembly module defined in its text format imports it. This only uses the text format for demonstration purposes, to show you what's going on. It is likely, you will use another language to compile a Wasm (WebAssembly Module) binary, such as TinyGo. Regardless of how wasm is produced, the export/import mechanics are the same!
Where next?
The following examples continue the path of learning about importing and exporting functions with wazero:
WebAssembly System Interface (WASI)
This uses an ad-hoc Go-defined function to print to the console. There is an emerging specification to standardize system calls (similar to Go's x/sys) called WebAssembly System Interface (WASI). While this is not yet a W3C standard, wazero includes a wasi package.