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

Could the binary AST be...a bit more binary? #72

Open
dead-claudia opened this issue Feb 20, 2019 · 1 comment
Open

Could the binary AST be...a bit more binary? #72

dead-claudia opened this issue Feb 20, 2019 · 1 comment

Comments

@dead-claudia
Copy link

I'm revisiting this proposal a few months later, and I'm wondering: could this proposal be better specified in terms of raw bytes? Currently, it seems largely spec'd in terms of a JSON-like format, but IMHO that doesn't really seem like it's as small as it could be. For one, it could leverage LEB128 much like WASM does and in a similar fashion. It also doesn't need to keep type names or even operator names as strings, so I feel being a bit more binary could realize the proposal's intent a little better.

@Yoric
Copy link
Collaborator

Yoric commented Feb 20, 2019

We're working on the serialization format separately. It's not ready for proposal yet, as we've been trying a number of very different techniques.

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

2 participants