Closed morenol closed 1 year ago
I think you are overthinking it. It looks quite easy to me:
wasm32-unknown
is for browserswasm32-wasi
is for other VMs that have access to binary interfacesAlso, let's try to not duplicate pipelines in tests, once we run cargo tests --all-features
for each target isn't it enough? What is CI / check_features (ubuntu, --features serde) (pull_request)
about?
I think you are overthinking it. It looks quite easy to me:
wasm32-unknown
is for browserswasm32-wasi
is for other VMs that have access to binary interfacesAlso, let's try to not duplicate pipelines in tests, once we run
cargo tests --all-features
for each target isn't it enough?
In Fluvio we use wasm32-unknown-unknown with wasmtime. I think that should not assume that thing since wasm32-unknown-unknown is supported by wasmtime
Interesting, which VMs you support for Wasm32? Why you don't use Wasi?
We recently added support for WASI, but still is not enabled by default, we could consider to migrate to only use WASI in the feature but that decission has not been taken yet
Fixes #
Checklist
Current behaviour
New expected behaviour
Change logs