find: switch to deque for recent line storage #1910
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.
Description
Besides giving us roughly O(1) performance for appends instead of O(n), we also get automatic trimming of old entries.
Since I was already switching things up, I also eliminated the need to reverse the list (now deque) of lines before iterating through it when executing the find-and-replace operation. Lines are now stored in reverse chronological order.
Checklist
make qa
(runsmake quality
andmake test
)Notes
I'm letting Travis do the QA checks, and will update that checkbox later.
@cottongin first suggested the idea, and expressed interest in helping test this change. I did do basic testing myself (including inspecting the data in memory with the ol' ipython plugin).
Probably should revisit a couple of my own plugins that also store recent messages like this and convert them over, since I just lazily copied find's logic.