In iOS development there are moments where you ask yourself: “To weak, or not to weak, that is the question”. Let’s see how “to weak” with the arrays.
Overview
In this article, I speak about memory management without explaining it since it would be beyond the goal of this article. The official documentation is a good starting point to learn this subject. Then, if you have other doubts, please leave a comment and I’ll reply as soon as possible.
Array is the most popular collection in Swift. By default, it maintains a strong references of its elements. Even if this behaviour is useful most of the time, you might have some scenarios where you would want to use weak references. For this reason, Apple provides an alternative to Array which maintains weak references of its elements: NSPointerArray.
Before looking at this class, let’s see and example to understand why we should use it.
Why Weak References?
Let’s use, as example, a ViewManager class which has two properties of type View. In its constructor, we add these views in an array to inject inside Drawer—which uses this array to draw something inside the views. Finally, we have a method destroyViews to destroy the two Views:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 | class View { } class Drawer { private let views: [View] init(views: [View]) { self.views = views } func draw() { // draw something in views } } class ViewManager { private var viewA: View? = View() private var viewB: View? = View() private var drawer: Drawer init() { self.drawer = Drawer(views: [viewA!, viewB!]) } func destroyViews() { viewA = nil viewB = nil } } |
Unfortunately, destroyViews doesn’t destroy the two views because the array inside Drawer is maintaining a strong reference of the views. We can avoid this problem replacing the array with a NSPointerArray.
NSPointerArray
NSPointerArray is an alternative to Array with the main difference that it doesn’t store an object but its pointer (UnsafeMutableRawPointer).
This type of array can store the pointer maintaining either a weak or a strong reference depending on how it’s initialised. It provides two static methods to be initialised in different ways:
1 2 3 | let strongRefarray = NSPointerArray.strongObjects() // Maintains strong references let weakRefarray = NSPointerArray.weakObjects() // Maintains weak references |
Since we want an array of weak references, we’ll use NSPointerArray.weakObjects().
Now, we can add a new object in this array:
1 2 3 4 5 6 7 8 | class MyClass { } var array = NSPointerArray.weakObjects() let obj = MyClass() let pointer = Unmanaged.passUnretained(obj).toOpaque() array.addPointer(pointer) |
Since using the pointer may be annoying, you can use this extension which I made to simplify the NSPointerArray:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | extension NSPointerArray { func addObject(_ object: AnyObject?) { guard let strongObject = object else { return } let pointer = Unmanaged.passUnretained(strongObject).toOpaque() addPointer(pointer) } func insertObject(_ object: AnyObject?, at index: Int) { guard index < count, let strongObject = object else { return } let pointer = Unmanaged.passUnretained(strongObject).toOpaque() insertPointer(pointer, at: index) } func replaceObject(at index: Int, withObject object: AnyObject?) { guard index < count, let strongObject = object else { return } let pointer = Unmanaged.passUnretained(strongObject).toOpaque() replacePointer(at: index, withPointer: pointer) } func object(at index: Int) -> AnyObject? { guard index < count, let pointer = self.pointer(at: index) else { return nil } return Unmanaged<AnyObject>.fromOpaque(pointer).takeUnretainedValue() } func removeObject(at index: Int) { guard index < count else { return } removePointer(at: index) } } |
Thanks to this extension, you can replace the previous example with:
1 2 3 4 5 | var array = NSPointerArray.weakObjects() let obj = MyClass() array.addObject(obj) |
If you want to clean the array removing the objects with value nil, you can call the method compact():
1 2 | array.compact() |
At this point, we can refactor the example used in “Why Weak References?” with the following code:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | class View { } class Drawer { private let views: NSPointerArray init(views: NSPointerArray) { self.views = views } func draw() { // draw something in views } } class ViewManager { private var viewA: View? = View() private var viewB: View? = View() private var drawer: Drawer init() { let array = NSPointerArray.weakObjects() array.addObject(viewA) array.addObject(viewB) self.drawer = Drawer(views: array) } func destroyViews() { viewA = nil viewB = nil } } |
Note:
- You may have noticed that
NSPointerArraystores pointers ofAnyObjectonly, it means that you can store just classes—so neither structs nor enums. You can store protocols if they have the keywordclass:12protocol MyProtocol: class { } - If you want to play with
NSPointerArray, I suggest you to avoid the Playground since you may have odd behaviours with the retain count. A sample app would be better.
Alternatives
NSPointerArray is very useful to store objects maintaining weak references, but it has a problem: it’s not type-safe.
For “not type-safe”, I mean that the compiler is not able to infer the type of the objects inside NSPointerArray, since it uses pointers of objects AnyObject. For this reason, when you get an object from the array, you must cast it to your object type:
1 2 3 4 | if let firstObject = array.object(at: 0) as? MyClass { // Cast to MyClass print("The first object is a MyClass") } |
object(at:) comes from my NSPointerArray extension which I shown previously.
If we want to use a type-safe alternative we can’t use NSPointerArray anymore.
A possible workaround is creating a new class WeakRef with a generic weak property value:
1 2 3 4 5 6 7 8 9 | class WeakRef<T> where T: AnyObject { private(set) weak var value: T? init(value: T?) { self.value = value } } |
private(set) exposes value in read-only mode, in this way no one can set its value from outside the class.
Then, we can create an array of WeakRef, where value is your MyClass object to store:
1 2 3 4 5 6 | var array = [WeakRef<MyClass>]() let obj = MyClass() let weakObj = WeakRef(value: obj) array.append(weakObj) |
Now, we have an array type-safe which maintains a weak reference of your MyClass objects. The disadvantage of this approach is that we must add an extra layer in our code (WeakRef) to wrap the weak reference in a type-safe way.
If you want to clean the array removing the objects with value nil, you can write the following method:
1 2 3 4 | func compact() { array = array.filter { $0.value != nil } } |
filter returns a new array with the elements that satisfy the given predicate. You can find more details in the documentation.
Now, we can refactor the example used in “Why Weak References?” with the following code:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | class View { } class Drawer { private let views: [WeakRef<View>] init(views: [WeakRef<View>]) { self.views = views } func draw() { // draw something in views } } class ViewManager { private var viewA: View? = View() private var viewB: View? = View() private var drawer: Drawer init() { var array = [WeakRef<View>]() array.append(WeakRef<View>(value: viewA)) array.append(WeakRef<View>(value: viewB)) self.drawer = Drawer(views: array) } func destroyViews() { viewA = nil viewB = nil } } |
A cleaner version using the typealias:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | typealias WeakRefView = WeakRef<View> class View { } class Drawer { private let views: [WeakRefView] init(views: [WeakRefView]) { self.views = views } func draw() { // draw something in views } } class ViewManager { private var viewA: View? = View() private var viewB: View? = View() private var drawer: Drawer init() { var array = [WeakRefView]() array.append(WeakRefView(value: viewA)) array.append(WeakRefView(value: viewB)) self.drawer = Drawer(views: array) } func destroyViews() { viewA = nil viewB = nil } } |
Dictionary And Set
This article has the main focus on Array, if you need something similar to NSPointerArray for Dictionary you can have a look at NSMapTable, whereas for Set you can use NSHashTable.
If you want a type-safe Dictionary/Set, you can achieve it storing a WeakRef object.
Conclusion
I guess you are not going to use arrays with weak references very often, but it’s not an excuse not to know how to achieve it. In iOS development the memory management is very important to avoid memory leaks, since iOS doesn’t have a garbage collector. ¯\_(ツ)_/¯
06/06/2017 at 13:03
Hi Marco, Nice article and very good written! Good job! But I really wonder where we could use it? In example above it is enough just add some drain() function in Drawer class and call it in destroyViews() method.
06/06/2017 at 13:10
Hi Oleg,
Thank you, I’m glad you like the article. I use an example which I used recently: an array of observers https://github.com/MarcoSantarossa/SwiftyToggler/blob/develop/Source/FeatureChangesObserversPool/FeatureChangesObserversPool.swift
I had an array of observers to notify when the data changes. To achieve it I used a Set of elements with weak references. In this way I didn’t increase the retain count of the observers.
Does it make sense to you? Or would you use a better approach?
06/06/2017 at 15:38
Thank you for you reply!
I see only two reasons to use weak references in your example:
when you don’t have access to the collection (observersPool), so you can’t remove object from the collection.
when you do not want to care about removing object from the collection.
But I can see you have removeObserver(..) method, so case #2 only? Or I missed something?
PS^ Looks like NSNotificationCenter uses strong references, that is why they remind us do not forget to call removeObserver 🙂
06/06/2017 at 15:54
Yep the case #2 is right. I used the weak reference because if for some reasons I have to destroy the object “observer” I’m able to do it without caring of removing it with
removeObserver. I’ve forgotten too many times to call theremoveObserverofNSNotificationCenter😅14/05/2017 at 08:10
Function compact can be rewritten
array.flatMap { $0.value } to return array without nills
14/05/2017 at 09:37
Hi Roman,
Thank you for the proposal.
I may be wrong, but
flatMapis used to transform an array of element A to an array of element B removing the element nil. It means that with that code we transform an array ofWeakRefto an array ofMyClassnot-nil, we can test it with it:We can use this higher-order function also to filter the nil elements, but it works just with
$0since you are going to transform the array of element A to an array of element A not-nil.We can use
array.flatMap { $0 }to remove all nilWeakRef, but we cannot use it to remove allWeakRefwithvalueto nil.Does it make sense to you? Did I misunderstand the comment?
10/05/2017 at 02:58
What a nice article to read! Very informative and well written. Thank you, it helped me a lot.
10/05/2017 at 07:45
Hi Charles, I’m glad you like the article. Thank you very much!!