On Apr 15, 2014, at 7:45 AM, Alex Zavatone <z...@mac.com> wrote: > A good approach here would be to make a test case for NSArray and NSSet, a > known set of files and simply test now long each takes.
In general I agree that it’s a good idea to test before optimizing. It’s common for people here to start obsessing over performance without even knowing whether the unoptimized code will take a measurable amount of time. But in this case, there are enough red flags (scanning the filesystem, which often contains millions of files, and doing string comparisons against thousands of patterns), and using an NSSet instead of an NSArray is such an easy change, that I consider it a no-brainer to go with NSSet. —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
