You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
The WASI ecosystem is evolving quickly, for example with Rust 1.41.0 using wasi_snapshot_preview1 rather than wasi_unstable. To keep up, we are going to either have to keep moving to the latest version of WASI, or else start supporting multiple versions. Sticking to the latest version will mean breaking backwards compatibility for older modules, but supporting multiple versions will be complex.
Further complicating this is the fact that some parts of the ecosystem are yielding Wasm binaries that import multiple WASI snapshots. For example, a Rust program compiled with 1.40.0 that uses wasi = "0.9.0" as a dependency will include imports for both wasi_snapshot_preview1 and wasi_unstable. This kind of scrambles my brain, because it's like compiling a native program against multiple libcs, but I believe @pchickey has some ideas for how we might cut through some of the complexity with witx and wiggle.
The text was updated successfully, but these errors were encountered:
I do think support multi-version is necessary for the Backward compatibility reason. and version can be limit as 3 or 4 versions. with separated folders for easy compiling.
ifyouseewendy
added a commit
to ifyouseewendy/as-playground
that referenced
this issue
Dec 9, 2020
The WASI ecosystem is evolving quickly, for example with Rust 1.41.0 using
wasi_snapshot_preview1
rather thanwasi_unstable
. To keep up, we are going to either have to keep moving to the latest version of WASI, or else start supporting multiple versions. Sticking to the latest version will mean breaking backwards compatibility for older modules, but supporting multiple versions will be complex.Further complicating this is the fact that some parts of the ecosystem are yielding Wasm binaries that import multiple WASI snapshots. For example, a Rust program compiled with 1.40.0 that uses
wasi = "0.9.0"
as a dependency will include imports for bothwasi_snapshot_preview1
andwasi_unstable
. This kind of scrambles my brain, because it's like compiling a native program against multiple libcs, but I believe @pchickey has some ideas for how we might cut through some of the complexity withwitx
andwiggle
.The text was updated successfully, but these errors were encountered: