Instead, Rust parsers (that are also wasm-compatible) should be used. We can then use wasm_bindgen to bind a JS Uint8Array to a Rust &[u8] to pass source data to such libraries. This should improve performance, especially when ingesting large data files.
This will also allow ggsql-wasm to build for native targets as well as wasm32-unknown-unknown, though really I don't know how useful such a build actually is, other than perhaps for testing.
Instead, Rust parsers (that are also wasm-compatible) should be used. We can then use wasm_bindgen to bind a JS
Uint8Arrayto a Rust&[u8]to pass source data to such libraries. This should improve performance, especially when ingesting large data files.This will also allow ggsql-wasm to build for native targets as well as
wasm32-unknown-unknown, though really I don't know how useful such a build actually is, other than perhaps for testing.