Takeshi Yoneda

xpost from the Gopher Slack (https://gophers.slack.com/archives/C04CG4A2NKX/p1685438483389279) > FYI for anyone interested - I have started the long journey of our optimizing compiler backend which may multiple months to reach stability...

I think the question is answered: we are actually heading towards the optimizing compiler which I expect to take us multiple months even a year or so before it reaches...

curious what's left to close this?

how about just using pod labels to switch application's behavior between primary and canary (for example, use separated databases for primary/canary)? We can embed labels by `fieldRef` to environment variables.

relevant: https://github.com/tetratelabs/wazero/pull/1815

https://github.com/tetratelabs/wazero/actions/runs/8077516060/job/22067963967?pr=2099 this hasn't been resolved yet I think

https://github.com/tetratelabs/wazero/compare/wrapaerrr?expand=1 how about this? This will output like this: ``` $ wazero run ./zig-out/bin/main.wasm reached unreachable code wasm stack trace: wasi_snapshot_preview1.proc_exit(i32) .os.exit(i32) 0x329: /Users/mathetake/zig-macos-aarch64-0.11.0-dev.1499+23b7d2889/lib/std/os.zig:616:23 .os.abort() 0x1b9: /Users/mathetake/zig-macos-aarch64-0.11.0-dev.1499+23b7d2889/lib/std/os.zig:553:13 .builtin.default_panic(i32,i32,i32,i32) 0x86: /Users/mathetake/zig-macos-aarch64-0.11.0-dev.1499+23b7d2889/lib/std/builtin.zig:863:25...

The output above is for `.os_tag = .wasi` and the current output is like this (no trace, just a message): ``` $ wazero run ./zig-out/bin/main.wasm reached unreachable code ```

https://github.com/tetratelabs/wazero/pull/2177

I would appreciate it if you could fix it ;)