vercel-labs / vercel-labs/native
feat: JSONL with future.cancel <> AbortSignal binding layer for streaming/iterating data
Nobody has claimed this yet.
- Dominant language
- Zig
- Stars
- 7.7k
- Forks
- 314
- Avg merge
- 5h
- Merged PRs (30d)
- 13
Description
a minor extension of the JSON bridge for JSONL style streaming behaviour and getting fetch cancellation traveling across the boundary by having the zig side return a future and calling future.cancel()on abort.
The future.cancel() and AbortSignal part of the approach could apply to the existing JSON bridge for non iterating/streaming data that still runs long enough that frontend based cancellation on some cases will make sense.
Contributor guide
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 by tracing the existing JSON bridge and its handling of streaming or iterating data. Examine how AbortSignal reaches the Zig side and how future.cancel() could be connected; done means JSONL streaming supports cancellation across the boundary, with the approach also considered for long-running non-streaming JSON operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- zig
- Domain
- api, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100