What is ARC and how does it work?

21 Tem 14:41

ARC explains how it works by sharing a useful reminder I encountered in one of my Swift projects. ARC, or *Automatic Reference Counting*, is a mechanism that automates memory management: every time a new reference is created (e.g., `let a = Class()`), ARC increments the object's reference count; when references are lost (end of scope, variable set to `nil`, etc.), it decrements the count and deallocates the object when the count reaches zero. This significantly impacts performance because it eliminates the need for manual `retain/release` calls—Swift’s compiler inserts these at compile-time. Especially when working with UI animations or Core Data, ARC makes detecting memory leaks much easier; otherwise, I’d end up with crashes at runtime because a deallocated `UIViewController` still had references to its UI elements. Strong references are the default and directly control an object’s lifespan (excluding `@escaping` closures), while weak references establish a non-owning connection without incrementing the reference count—commonly used in delegate patterns. For example, when a TableViewController is dismissed, setting its delegate to `nil` prevents memory leaks. Unowned references, unlike weak, are used when you can guarantee the referenced object will never be `nil`; for instance, in parent-child relationships where the child is certain the parent exists, ensuring the parent remains alive during garbage collection. Early in my projects, I ran into issues with unowned references—when the parent was deallocated, the child tried accessing its parent reference and crashed. Switching to weak solved the problem. While ARC’s fine-tuning can be confusing at first, once you get used to it, it speeds up the development process and minimizes stress around memory management.