Conversation
Spxg
force-pushed
the
cov
branch
3 times, most recently
from
d16f721 to
c2b832e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Do we need to implement
js-bindgen-covdirectly insidejs-bindgen-test? My main concern is how custom targets would use it.And for custom targets, how can we ensure they are linked to
minicov? In other words, how should we handle theensure_linkedworkaround. The best approach would be to customizelibrary/profiler_builtins, but there doesn’t seem to be any precedent for that.