After some testing, I don't see a case where the crop rotation de-duplicator is better compared to the mark and sweep default algorithm. Also the documentation is quite sparse, but states "This deduplicator is probably inferior to the {@link SweepDeduplicator}." and doesn't state when it could be useful.
Since the low (no?) number of issue about this specific dedup algorithm, I think it's not really used. So I propose we deprecate/delete it
After some testing, I don't see a case where the crop rotation de-duplicator is better compared to the mark and sweep default algorithm. Also the documentation is quite sparse, but states "This deduplicator is probably inferior to the {@link SweepDeduplicator}." and doesn't state when it could be useful.
Since the low (no?) number of issue about this specific dedup algorithm, I think it's not really used. So I propose we deprecate/delete it