hyperlight-dev / hyperlight-dev/hyperlight-sandbox
Further consolidation of wasi interfaces and sharing it across backends
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 73
- Forks
- 7
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 23
Description
We should be able to use Hyperlight's wit bindings system (see https://github.com/hyperlight-dev/hyperlight/blob/main/src/hyperlight_host/tests/wit_test.rs) to provide a host and guest side implementations. This would allow Javascript and Wasm to share the same host side bindings and similar guest apis.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/hyperlight_host/tests/wit_test.rs, the WIT bindings example named in the issue. Compare how host and guest implementations are represented, then determine how the same host-side bindings and corresponding guest APIs can be shared by the JavaScript and Wasm backends. Done means both backends use the consolidated interface without separate equivalent bindings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust, wasm
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100