fix(liveslots): collection.clear(pattern) vs getSize #10008
Merged
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.
The
.clear()
method, on (strong) collections, will delete all entries. But it can also be called withkeyPatt
and/orvaluePatt
argument, and only the matching entries will be deleted.Previously, the
|entryCount
metadata field was unconditionally set to zero for any call to.clear()
, even those with patterns which caused some entries to be retained. This caused a subsequentcollection.getSize()
to return the wrong value, yielding zero even if the collection still had entries.This commit fixes the logic to decrement the
|entryCount
field by the number of entries actually deleted. As an optimization, it is still set directly to zero ifclear()
is not limited by patterns.fixes #10007