Rework Vector_softRemove() and compact() operations #1782
+48
−58
Conversation
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
Use a goto label when a table row should be removed. No changes to code behavior.
Remove the 'dirty_index' and 'dirty_count' members of Vector object. Let the caller of the Vector_softRemove() operation track the 'dirtyIndex' and pass it to Vector_compact() when needed. 'dirtyIndex' is supposed to have shorter lifespan than a Vector instance, and by removing the member we can save object size. 'dirty_count' is redundant and thus removed as well. A boolean 'isDirty' member is added to a Vector object for ease of debugging. Signed-off-by: Kang-Che Sung <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a follow-up of commit 08166b2
This frees up the need of
dirty_indexanddirty_countmembers ofVectorobject. These two members are not supposed to last long and are only useful in keeping the state between thesoftRemove()andcompact()operations.Rework the two operations so that the caller would keep the
dirtyIndexwhen callingsoftRemove()and passdirtyIndexto thecompact()in the final step.The new
dirtyIndexis safe to migrate to usingsize_tas I don't use any negative value of it.