Single file info instance and caching
Duplicate/unique file analyzer with at-a-glance statistics.
Brought to you by:
rknopman
Consider having a single file info (internal) object to store information for all files. This would also serve as a cache from one search to the next. This supports the use case of swapping left and right side directories and rerunning a search. All the files have already been searched, so gathering of file info is redundant.
A cache could be stored in the file system between runnings of DupStat. For slow-speed disk (e.g., network drives, USB < 3 drives), it can take a long time to gather file info for a large directory tree.
But then, would need UI and functionality to manage the cache, make it optional, clear it, etc. Also need to make a service or function to keep the cache fresh.