Add support for WASI p2.
TODOs (potentially incomplete):
WasiCtxBuilder has settings where the user can inject an implementation, e.g. socket_addr_check. Ideally, we'd allow Ruby blocks to define such implementations. But unsure how we can achieve this: calling an arbitrary Ruby block is faillible, and the implementations do not allow for failure. Given this challenge, I'd suggest skipping those config knobs initially.
Add support for WASI p2.
TODOs (potentially incomplete):
wasi_commoncrate withwasmtime_wasiinherit_network,allow_ip_name_lookup,allow_udp,allow_tcpWasiCtxBuilder has settings where the user can inject an implementation, e.g. socket_addr_check. Ideally, we'd allow Ruby blocks to define such implementations. But unsure how we can achieve this: calling an arbitrary Ruby block is faillible, and the implementations do not allow for failure. Given this challenge, I'd suggest skipping those config knobs initially.