bytecodealliance / bytecodealliance/WASI-Virt
Migrate to WASI p3
Open
- Dominant language
- Rust
- Stars
- 235
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Per [this discussion](https://github.com/bytecodealliance/WASI-Virt/pull/161#issuecomment-4893808562) on https://github.com/bytecodealliance/WASI-Virt/pull/161, `WASI-Virt` needs to migrate to p3 in order to be able to properly support semver dependency matching, as well as to benefit from `async`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the discussion linked from issue #162 and the changes in pull request #161 to understand the required WASI p3 migration. Identify the current WASI-Virt entry points and validation coverage, then verify that semver dependency matching and async support work after the migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100