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.
Since I keep an archive of submissions from previous years and compare the current submissions also against them, I've been getting a huge number of matches between each and every submission in the results - most of them uninteresting.
To fix this issue, I propose a feature allowing distinguishing new submissions from the old ones (loaded with -a option, for archival) - new submissions will be compared with each other, and also compared against the old submissions, but there won't be comparisons of the old ones with each other. This approach reduces both the clutter in the search results and the running time.
At extreme this might be used for n-to-1 comparisons, i.e. comparing a particular submission against the whole archive.
Please review & merge.