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

Optimize Pre-compilation Format #318

Open
chadhietala opened this issue Sep 16, 2016 · 0 comments
Open

Optimize Pre-compilation Format #318

chadhietala opened this issue Sep 16, 2016 · 0 comments
Assignees

Comments

@chadhietala
Copy link
Member

chadhietala commented Sep 16, 2016

In the compiled output we currently send down a lot strings that get mapped into runtime syntax objects. While this works and is an extremely large improvement over Glimmer1's output we still have headroom here for further optimizations.

In the short term we should keep an enum in Glimmer that maps an opcode name to a string. In the long term we may want to investigate going further down the byte-array path.

@chadhietala chadhietala self-assigned this Sep 16, 2016
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