-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
feat(compiler): Name globals in wasm output #1184
Conversation
0c03f16
to
8902675
Compare
a4b6d47
to
eb80b16
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can only say LGTM!
ff243e2
to
0133a2d
Compare
eb80b16
to
e058860
Compare
0133a2d
to
9b0a798
Compare
e058860
to
9d79ac7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
9d79ac7
to
8c00ba2
Compare
8c00ba2
to
1947283
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the code cleanup 🎉
This is more code cleanup than anything else, largely from old logic we needed back before we used Binaryen. Additionally, it'll make it easier for us to debug what's going in in the wasm output since we'll actually see the names of globals getting assigned rather than just
global_0
etc.