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
refactor: extract CCheckQueue's data handling into a separate container "Bag" #27331
base: master
Are you sure you want to change the base?
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsNo conflicts as of last run. |
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.
Approach ACK 6b0537c
Needs trivial rebase, an adjacent Makefile entry and include header.
This introduces a simple container where elements can be added and removed. The order of element removal is not specified and might change in future due to e.g. optimizations. The logic for that container is purely copied from CCheckQueue's current implementation of the queue.
This simplfies CCheckQueue's Loop by using the new Bag container.
ACK 6a9c6ea |
CCheckQueue
has stored its work items in aqueue
, but made no guarantee about the order of elements in that container. This PR extracts that data storage handling into a separate container classBag
. This is pure refactoring, the result should have a better separation of concerns, adds tests for the new container, and makes it now easier to separately test and optimize the container.