You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A standalone crate with access to the AST will then act as the "IR" for wasm-bindgen. Three new crates, wasm-bindgen-parser-{proc_macro,webidl,typescript} would parse their input into the AST and then generate Rust tokens (a Rust program) from the AST.
@fitzgen is working on the first part of splittng out the ast module into a new crate, and then I'll file issues for new parser crates to exist.
The text was updated successfully, but these errors were encountered:
In preparation for https://github.com/alexcrichton/wasm-bindgen/issues/18 and https://github.com/alexcrichton/wasm-bindgen/issues/42 @fitzgen and I have been talking about concrete next steps. We think the best way to implement this will be to split out the
ast
module (andToTokens
implementations) from thewasm-bindgen-macro
crate.A standalone crate with access to the AST will then act as the "IR" for wasm-bindgen. Three new crates,
wasm-bindgen-parser-{proc_macro,webidl,typescript}
would parse their input into the AST and then generate Rust tokens (a Rust program) from the AST.@fitzgen is working on the first part of splittng out the
ast
module into a new crate, and then I'll file issues for new parser crates to exist.The text was updated successfully, but these errors were encountered: