refactor: change the architecture to allow different search backends #131
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.
Right now this solves no issue, but I want to experiment with adding more search backends in the future. For this to be easier, it's probably good to have an idea of what a "backend" actually is 🙂
I think they can help solve performance issues in massive repositories. For example, I found out that "git grep" is much faster than ripgrep in some cases (5s vs 40s).
Related to #110