@jmoody, as I understand it, there is nothing different about how timers are handled in Swift vs. Objective-C. The runloop that manages the timer creates a strong reference to the timer, so it is not sufficient to 'nil out' a controllers reference to the timer. You must invalidate it. Thanks for the heads up there!
AFAIK a "new and improved standard library" is not one of the advertised features of Swift. You can generally expect the behavior of Foundation libraries to have the same behavior whether you're calling them from Swift or ObjC.
Solves #3
@jmoody, as I understand it, there is nothing different about how timers are handled in Swift vs. Objective-C. The runloop that manages the timer creates a strong reference to the timer, so it is not sufficient to 'nil out' a controllers reference to the timer. You must
invalidateit. Thanks for the heads up there!AFAIK a "new and improved standard library" is not one of the advertised features of Swift. You can generally expect the behavior of Foundation libraries to have the same behavior whether you're calling them from Swift or ObjC.