Pat Hickey

Can you post `v0.2.0-draft2` as well with the current contents of main? I'm working on an implementation and would like to manage the wit with `wkg`. Right now the ghcr.io...

@mikkelhegn there is no version 0.1.0 of this spec. By convention, the first release version of this spec would be 0.2.x, to match with the rest of the WASI 0.2...

`wasmtime-wasi-http` is wasmtime's host implementation of wasi-http, whereas this crate (wasi-rs) is for exposing wasi-http (and other wasi proposals) to guests, so that work won't be relevant here. I'd be...

> My current usecase is actually plugging in the IncomingRequest type to external ecosystem crates (e.g constructing an axum router and dispatching it on a single request). Because you are...

The get-stdout/err pattern was designed to be called multiple times because, as @badeend says, multiple independent libraries are compiled into the same component and all need their writes to make...

if ErrorContext is a pub type that impls std::error::Error, then you can use anyhow::Error in the interface to the user's Rust, and try downcasting it to ErrorContext in the implementation...

Like Alex, the only understanding I have of this topic is from PR 81 on the spec. It is quite possible that both the spec and our implementation are questionable,...

Agreed with Alex: implementing p1 on top of p2 is an important direction. There are some places we are choosing to do that with low fidelity (the whole rights system...

We used to have a more dynamic trait system to make this pluggable when wasmtime-wasi was backed by wasi-common, and when we rewrote wasmtime-wasi to detach it from the legacy...

Symbols will be duplicated if you call the `wasmtime_wasi::add_to_linker_*` functions directly, because those put all symbols into the linker. If you drop down to using the individual `wasmtime_wasi::bindings::::::add_to_linker_get_host` (see https://github.com/bytecodealliance/wasmtime/blob/main/crates/wasi/src/lib.rs#L356-L385...