-
Notifications
You must be signed in to change notification settings - Fork 695
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
Tooling: JS+wasm dead code stripping #434
Conversation
As discussed in #230.
Do you think there is something actionable within the design repo? There are a lot of interesting questions in the toolchain design space (design of .o files and static link libraries that incorporate JS); I wonder if a new repo containing docs describing the design of the toolchain (into which the new llvm-wasm backend fits) would make sense. |
Oh excuse me, I thought this was an issue, I didn't see it was a PR! |
lgtm |
@@ -44,6 +44,12 @@ The tooling we expect to support includes: | |||
- Instrumentation-based. | |||
* Process dump: local variables, call stack, heap, global variables, list of | |||
threads. | |||
* JavaScript+WebAssembly size optimization tool. Some developers have huge |
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.
lgtm, but all the other bullet points are a name + :
. Perhaps change the first .
to :
? In which case, maybe also edit to remove the later :
to avoid repetition.
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.
Good point. I updated the sentence, and shortened it so it fits better with the surrounding.
lgtm |
Tooling: JS+wasm dead code stripping
As discussed in #230.