bytecodealliance / bytecodealliance/wasi-rs
Publish wasi-nn Rust bindings here?
- Dominant language
- Rust
- Stars
- 370
- Forks
- 65
- Avg merge
- 7m
- Merged PRs (30d)
- 3
Description
I would like to publish Rust bindings for wasi-nn that were generated with the `witx-bindgen` tool in this repo (the Rust bindings currently live in [a Wasmtime example](https://github.com/bytecodealliance/wasmtime/tree/main/crates/wasi-nn/examples/wasi-nn-rust-bindings)). It would be helpful to me to have the bindings in one place--i.e., most likely this repository--so that changes to WITX, the tools, etc., can be tested against bindings from several modules. This would simplify creating and maintaining WASI proposals and there are other WASI proposals (e.g. wasi-crypto, wasi-sockets, etc.) that might benefit from this same idea.
The first question is "should this be done?" and I am interested in opinions here. Then, "how?": I think this repository (and accompanying CI tasks) could be slightly refactored to generate and publish multiple crates, one per proposal. Thoughts?
Contributor guide
Research direction
Start by comparing the Rust bindings in the linked Wasmtime wasi-nn example with this repository and inspect the existing CI tasks and WITX generation flow. Determine whether the repository should publish one crate per proposal and define how changes to WITX and witx-bindgen would be tested across proposals; done requires an agreed design before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100