Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split out the AST/parser code #88

Closed
alexcrichton opened this issue Mar 29, 2018 · 1 comment
Closed

Split out the AST/parser code #88

alexcrichton opened this issue Mar 29, 2018 · 1 comment

Comments

@alexcrichton
Copy link
Contributor

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 (and ToTokens implementations) from the wasm-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.

@alexcrichton
Copy link
Contributor Author

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

No branches or pull requests

1 participant