Swift version: 5.10
Unowned variables are similar to weak variables in that they provide a way to reference data without having ownership. However, weak variables can become nil
– they are effectively optional. In comparison, unowned variables must never be set to nil once they have been initialized, which means you don't need to worry about unwrapping optionals.
The most common place you'll see unowned variables is with closures that declare [unowned self]
– this means "I want to reference self
inside this closure but I don't want to own it." Why unowned
rather than weak
? Both would work, but let's face it: if self
is nil inside a closure, something has gone wrong!
SPONSORED Superwall lets you build & test paywalls without shipping updates. Run experiments, offer sales, segment users, update locked features and more at the click of button. Best part? It's FREE for up to 250 conversions / mo and the Superwall team builds out 100% custom paywalls – free of charge.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Available from iOS 7.0
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.