perf(coverage): cache current HitMap, reserve when merging #9469
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.
Avoid one of the two hashmap lookups in
CoverageCollector::step()
by caching the current contract's hashmap in a separate field. This unfortunately has to use a raw pointer and unsafe because self-referential structs are not possible.Additionally, add some
reserve
calls and initialize with some initial capacity to reduce the impact ofreserve(1)
inentry
calls.10-20% faster
forge coverage
on solmate.