A proposed WebAssembly System Interface API.
Phase 1
- Mendy Berger
- Sean Isom
TODO before entering Phase 2.
- Introduction
- Goals [or Motivating Use Cases, or Scenarios]
- Non-goals
- API walk-through
- Detailed design discussion
- Considered alternatives
- Stakeholder Interest & Feedback
- References & acknowledgements
This proposal is a collection of multiple interfaces.
| Interface | Description |
|---|---|
| wasi-webgpu | WebGPU interface for interacting with GPUs |
| wasi-frame-buffer | A CPU based graphics API |
| wasi-surface | A surface interface |
| wasi-graphics-context | A small interface connecting the graphics APIs (webgpu or frame-buffer) to surface |
[What is the end-user need which this project aims to address?]
[If there are "adjacent" goals which may appear to be in scope but aren't, enumerate them here. This section may be fleshed out as your design progresses and you encounter necessary technical and other trade-offs.]
The full API documentation can be found here.
[Walk through of how someone would use this API.]
[Provide example code snippets and diagrams explaining how the API would be used to solve the given problem]
[etc.]
[This section should mostly refer to the .wit.md file that specifies the API. This section is for any discussion of the choices made in the API which don't make sense to document in the spec file itself.]
[Talk through the tradeoffs in coming to the specific design point you want to make.]
// Illustrated with example code.
[This may be an open question, in which case you should link to any active discussion threads.]
[etc.]
[This section is not required if you already covered considered alternatives in the design discussion above.]
[Describe an alternative which was considered, and why you decided against it.]
[etc.]
TODO before entering Phase 3.
[This should include a list of implementers who have expressed interest in implementing the proposal]
Many thanks for valuable feedback and advice from:
- [Person 1]
- [Person 2]
- [etc.]