A WASM Plugin in Go (TinyGo)
The same greeter interface as the Rust,
Python, and JavaScript
guests, now in Go — compiled to a component with TinyGo and loaded through the
identical host path. Unlike the interpreted guests, this one is natively
compiled: the component is ~0.5 MB with no embedded runtime.
The worked example is the committed fixture tests/wasm-fixtures/greeter-go/,
verified by polyglot_go_guest_behaves_identically in crates/fidius-host.
Prerequisites
Section titled “Prerequisites”- TinyGo ≥ 0.41 (the standard
gocompiler can’t yet emit component-model exports; TinyGo can). TinyGo pulls in the matchinggotoolchain. wit-bindgen-go:go install go.bytecodealliance.org/cmd/wit-bindgen-go@latest.wasm-opt(binaryen) onPATH— TinyGo invokes it.
1. Generate bindings + implement
Section titled “1. Generate bindings + implement”wit-bindgen-go turns the WIT into a Go package with an Exports struct of
function fields; you assign your implementation to them. WIT type mapping:
s64/u64 → int64/uint64, list<u8> → cm.List[uint8],
result<T, _> → cm.Result[...] (built with cm.OK / cm.Err):
wit-bindgen-go generate -w greeter-plugin -o internal -p mymod/internal \ --cm go.bytecodealliance.org/cm path/to/greeter/wit// main.gopackage main
import ( greeter "mymod/internal/fidius/greeter/greeter"
"go.bytecodealliance.org/cm")
type addResult = cm.Result[greeter.PluginErrorShape, int64, greeter.PluginError]
func init() { greeter.Exports.Greet = func(name string) string { return "Hello, " + name + "!" } greeter.Exports.Add = func(a, b int64) addResult { return cm.OK[addResult, greeter.PluginErrorShape, int64, greeter.PluginError](a + b) } greeter.Exports.EchoBytes = func(data cm.List[uint8]) cm.List[uint8] { src := data.Slice() out := make([]uint8, len(src)) for i := range src { out[i] = src[len(src)-1-i] } return cm.ToList(out) } greeter.Exports.FidiusInterfaceHash = func() uint64 { return 0x0102030405060708 }}
func main() {}The interface hash must equal the descriptor’s (the host rejects a mismatch at load); signing — not this hash — is the security boundary.
2. Build the component
Section titled “2. Build the component”TinyGo’s runtime imports wasi:cli (e.g. wasi:cli/environment), so the
build world must declare those imports even though the greeter interface
itself uses none. Define a small local world that pulls them in and re-exports
the interface:
// wit/world.witpackage fidius:greeter-go@1.0.0;
world greeter-plugin { include wasi:cli/imports@0.2.0; export fidius:greeter/greeter@1.0.0;}Populate wit/deps/ with the WASI wit (TinyGo ships it under
$(tinygo)/lib/wasi-cli/wit) and the greeter interface, then build:
tinygo build -target=wasip2 --wit-package wit --wit-world greeter-plugin \ -o greeter_go.wasm .wasm-tools validate --features component-model greeter_go.wasm3. Package, sign, and load
Section titled “3. Package, sign, and load”Identical to any fidius package ([wasm].component = "greeter_go.wasm"). The host
loads it through the same load_wasm + descriptor as every other guest:
let handle = host.load_wasm("greeter-go-pkg", &Greeter_WASM_DESCRIPTOR)?;let greeting: String = handle.call_method(0, &("Ada".to_string(),))?;assert_eq!(greeting, "Hello, Ada!");