Hmm...when the memory checker came out for Xcode, I ran it on my code-base, parts of it decades old. I still haven't adopted ARC. I expected mayhem. Turns ou

Hmm...when the memory checker came out for Xcode, I ran it on my code-base, parts of it decades old. I still haven't adopted ARC. I expected mayhem. Turns out it "found" two false positives, i.e. leaks that are mandated by the low-level Objective-C APIs. I put the required incantations around them to shut up the checker and then I was good to go. Keeping it simple, I guess... ¯\_(ツ)_/¯ Oh, and back to my thesis about "safyeness"[1], I certainly felt much better about my code once those checks had passed, even though it hadn't changed. [1] https://blog.metaobject.com/2014/06/the-safyness-of-static-typing.html https://blog.metaobject.com/2014/06/the-safyness-of-static-t...