bytecodealliance / bytecodealliance/wasm-tools

Streaming reading in wasmparser

Open
#328 3 comments 0 reactions 0 assignees View on GitHub
wasmparser
Dominant language
Rust
Stars
1.8k
Forks
351
Avg merge
1d 6h
Merged PRs (30d)
46

Description

I looked at wasmparser and naively expected the API to work with a `std::io::BufReader` as input, rather than requiring the full file contents up front.

Is there something fundamental to the WASM format that precludes this? Was it an intentional design decision here to not use such a thing? Glancing at `binary_reader`, it seems it works with a cursor-like concept anyway.

Contributor guide

Open the contributing guide

Research direction

Start by reading wasmparser's binary_reader and the current input API to understand its cursor-like assumptions and whether BufReader is compatible. Determine whether streaming requires a design change or is precluded by the WASM format; document the conclusion and the intended API direction.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.