WebAssembly / WebAssembly/wasi-webgpu

Rust binding for this proposal

Open
#16 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
220
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Hi there, here's from WasmEdge runtime.

Take the WASI-NN proposal for example, there's rust binding generated from the witx format.
Developers can use the witx-bindgen to generate the rust binding easily.
With this generated library, developers can call the WASI proposal APIs in rust and compile into WASM.

But currently the WASI proposals provides the wit format, which can be compiled into component model.
For the other WebAssembly runtimes, supporting the component model is not so easy and quickly due to its complexity.
To support this proposal, we should have:

  • The ABI documentation in WASM, especially the host function parameter and return types in WASM.
  • The rust binding to this proposal, in order to generate the test WASM invoking the host functions of this proposal.

Unfortunately, this WASI-WebGPU proposal doesn't provide the information for the API doc, which is the most important to implement this proposal.
Can you help to provide the rust binding and API doc so that developers can try to compile the WASM files without component?
Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the WASI-WebGPU proposal and comparing its wit format with the WASI-NN example and generated witx Rust binding. Define the missing WASM ABI documentation, host function parameter and return types, and the Rust binding needed to generate test WASM without the component model. Done means developers can compile and use those bindings against the proposal.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
api, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.