Damian Gryski

This is basically https://github.com/tinygo-org/tinygo/issues/2735 ; the runtime isn't initialized.

Should we come up with some supported way to initialize the runtime so that this kind of behaviour is supported?

This is a known stack overflow issue. If possible, switch to a code-generation based regexps package like libfsm or ragel.

I tweaked the binary to run without javascript (but still wasm): ``` package main import ( "encoding/json" "fmt" ) var ( terminateChannel = make(chan struct{}) ) type Person interface {...

WASI default stack size is now 64K. I think we can tag this as "next-release".

We still need to update argument construction if we haven't already.

Ah yes, thanks. Was trying to figure out why I was getting this warning from wasmtime. Needed to rebase my branch against the latest `dev`: ``` ~/go/src/github.com/dgryski/bug/intf $ tinygo run...

Now we just need to unstub the 29 calls in `libc_wasip2.go` with Go implementations of the associated C calls using preview2 calls under the hood.

This is now in a state where it's roughly equivalent to wasip1 support. I still plan to add networking support, but that can come in a later PR.

Just rebased against `dev` with no conflicts; let see what happes...