At least once a day, it seems the Swift compiler loses its mind and generates ridiculous code. It often manifests as an unrecognized selector error, but usually the call stack looks completely wonky. Like, it'll be stopped in one method, but if you look at the call site, it's not calling that method at all.
Clean and rebuild always fixes this problem. At first I though it just had some dependency-tracking weakness, and wasn't recompiling a file when something in another file changed. But just now it happened, and the only thing I did was introduce a new method in one file and call it from the same file. Again, clean and build fixed it. Xcode 7.1.1, OS X 10.10.5, OS X app. Anyone else seeing this? I know if I write a bug, Apple's gonna ask for a project that reproduces it. I can't give them that. -- Rick Mann rm...@latencyzero.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
