The only reasonable solution I see to this problem is to actually track which files have already been scanned. I have implemented this in a way that should be very efficient (especially in terms of memory) using a tree-set designed specifically for paths. We should confirm that scan performance is not impacted significantly by this change, particularly when scanning larger filesystems.
The only reasonable solution I see to this problem is to actually track which files have already been scanned. I have implemented this in a way that should be very efficient (especially in terms of memory) using a tree-set designed specifically for paths. We should confirm that scan performance is not impacted significantly by this change, particularly when scanning larger filesystems.
Resolves #207