Adrian Cole

@lthibault yeah I think the mythical way is via `externref` mythical because nothing supports it. In lieu of that in wazero context is the dirty little secret which works fine...

Hi, there. I am curious if it is a strict requirement to use wasmtime-go? If not, you might consider wazero, which is the only WebAssembly runtime written in Go (even...

@tanjianfeng thanks for the note. For what you are mentioning, I think main gain for go folks is having a statically compiled binary and also being able to load extensions...

> Some of my colleagues want to add extensions into [mosn](https://github.com/mosn/mosn); I will recommend wazero to them. Thanks. I think [others had been interested in this also](https://github.com/mosn/proxy-wasm-go-host/issues/15). OTOH, now is...

@amscanne thanks for the kind words about wazero. About memory plumbing: Right now, we have apis for config and runtime, but not allocation of the underlying memory itself. All apis...

@daixiang0 cool I can do a UUID like https://github.com/wapc/wapc-go/blob/master/engines/wazero/wazero.go#L303 Should we start by assuming the wasm binary changes per request? or should we assume it doesn't?

OK I've refactored now, though feels there are some API glitches. Have a look at the impl and if there's any more stuff here I can do that before backfilling...

## At least a README should be made in how to generate the wasm one other thing I think would be helpful is that the "run" function isn't documented or...

cool. I'll polish this up where basic means URI rewrite. I'll go ahead and update the exported function name to "rewrite_request_uri", also, unless you've strong feelings towards "run"

note I hit an unrelated code land mine but back together and will pick this up tomorrow.