Skip to content

feat: prove host-native wasm JavaScript async parsing - #22

Open
gpeacock wants to merge 1 commit into
mainfrom
gpeacock/wasm-parse
Open

gpeacock wants to merge 1 commit into
mainfrom
gpeacock/wasm-parse

Conversation

@gpeacock

@gpeacock gpeacock commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

Add a standalone Wasm package exposing caller-driven parsing without
a Rust executor, Rust-to-JS async bridge, or WASI filesystem.

  • Expose resumable parsing with read requests and owned responses
  • Add Task::pending_read to reacquire suspended requests
  • Add a Promise-based driver with AbortSignal cancellation
  • Provide Node async file reads and a browser-compatible Blob adapter
  • Compare Wasm geometry summaries against native blocking Rust
  • Test event-loop progress, interleaving, errors, and buffer lifetimes
  • Add documentation, Node/web builds, and CI validation

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

Add a resumable C parsing API that returns read requests and accepts
host-supplied responses without invoking I/O callbacks or selecting a
Rust executor.

- Add Task::pending_read to reacquire suspended read requests
- Expose parser creation, resume, supply, failure, and result operations
- Define sequencing, ownership, cancellation, and terminal error behavior
- Add a pthread driver with output parity checks against blocking parsing
- Test request handling, input lifetimes, errors, and cancellation
- Document the parse-only scope and run the native proof in CI

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@gpeacock gpeacock changed the title feat(c-api): expose sans-I/O parsing for host-native scheduling feat: prove host-native wasm JavaScript async parsing Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant