wasi component runtime error: instance export `read` has the wrong type about cargo-component

[kajacx]

The easiest workaround is to use a matching wasmtime-wasi and wasmtime.

Ok, I managed to do that when using wasmtime from source. I will put a link to the code here in case anyone runs into the same issue, but it's kind of a mess.

[peterhuene]

The WASI adapter built into cargo-component is slightly newer than 11.0 (it's currently using commit 7b9189b), so the signatures aren't matching.

The easiest workaround is to use a matching wasmtime-wasi and wasmtime.

cargo-component needs a way to override the built-in adapters with explicitly specified ones, though. Let's track that as part of this issue.

[peterhuene]

Also, I expect to start sourcing the adapters from a registry soon (rather than building them directly into cargo-component) so that the version can be specified in Cargo.toml, defaulting to latest available, probably.

We're almost to the point where WASI wit packages and the adapters can be published.