b63d4e6dcd
Formerly, we introduced `wazero.Namespace` to help avoid module name or import conflicts while still sharing the runtime's compilation cache. Now that we've introduced `CompilationCache` `wazero.Namespace` is no longer necessary. By removing it, we reduce the conceptual load on end users as well internal complexity. Since most users don't use namespace, the change isn't very impactful.
Users who are only trying to avoid module name conflict can generate a name like below instead of using multiple runtimes:
```go
moduleName := fmt.Sprintf("%d", atomic.AddUint64(&m.instanceCounter, 1))
module, err := runtime.InstantiateModule(ctx, compiled, config.WithName(moduleName))
```
For `HostModuleBuilder` users, we no longer take `Namespace` as the last parameter of `Instantiate` method:
```diff
// log to the console.
_, err := r.NewHostModuleBuilder("env").
NewFunctionBuilder().WithFunc(logString).Export("log").
- Instantiate(ctx, r)
+ Instantiate(ctx)
if err != nil {
log.Panicln(err)
}
```
The following is an example diff a use of namespace can use to keep compilation cache while also ensuring their modules don't conflict:
```diff
func useMultipleRuntimes(ctx context.Context, cache) {
- r := wazero.NewRuntime(ctx)
+ cache := wazero.NewCompilationCache()
for i := 0; i < N; i++ {
- // Create a new namespace to instantiate modules into.
- ns := r.NewNamespace(ctx) // Note: this is closed when the Runtime is
+ r := wazero.NewRuntimeWithConfig(ctx, wazero.NewRuntimeConfig().WithCompilationCache(cache))
// Instantiate a new "env" module which exports a stateful function.
_, err := r.NewHostModuleBuilder("env").
```
Signed-off-by: Takeshi Yoneda <takeshi@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.
Replace Import
You may use WebAssembly modules that have imports that don't match your ideal packaging structure. wazero allows you to replace imports with different module names as needed, on a function granularity using ModuleConfig.WithImport.