Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fixes to build with Closure (--closure 1) #21385
Fixes to build with Closure (--closure 1) #21385
Changes from all commits
c993e3d
7cdee4f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 think it would be great to get test coverage for these changes. Perhaps we can add a
_closure
variant to one or more of the existing browser tests?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.
The existing tests are enough, but I'm guessing aren't being run with both
-sSTRICT
and--closure
. Looking at #20592 when this was introduced @kripken asks "Do we not have any assertions outside ofifdef ASSERTIONS
?" the answer is yes, and probably more than I fixed here.specialHTMLTargets
is not the same, that's a regular Closure issue, just rolled into this fix (because it was in front of me at the time).I don't mind taking a look, but it won't be in the next weeks, and it's probably asking a bigger question: what to do with
asserts
that aren't guarded and then silently ignored?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 agree adding tests would be good, but I think should not block this from landing as incremental progress towards that goal. Unless you disagree @sbc100 ?
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.
Yes, I'm fine with landing this. Especially now that it doesn't include the specialHTMLElements thing which was a little confusing to me (since its declared as an array but used like an object).