Closure-based stdio API for WASI
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Swift
- Stars
- 504
- Forks
- 37
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 44
Description
Current setup that requires file descriptors is an overkill when the host may need to process some data in memory, and monitoring pipe buffering limits is onerous. A closure-based API would be dramatically simpler and cover these use cases without requiring pipe/fd workarounds.
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
The issue names no files, tests, or entry points; begin by locating WasmKit’s WASI stdio and file-descriptor APIs. Define the closure-based interface and its in-memory and pipe-related behavior, then add coverage for the stated use cases and run the relevant test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift, wasm
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100