Memory Management
6 posts5 videos42m
9:10
If you have been paying attention, then you may have noticed that we haven't resolved the strong reference cycle we introduced between the root view controller and the settings view controller earlier in this series. This is what the implementation of the RootViewController class looks like.
6:49
In the previous episode of Understanding Swift Memory Management, you learned how weak and unowned references can break a strong reference cycle. What sets weak and unowned references apart from strong references? What is the difference between weak and unowned references? When is it appropriate to choose an unowned reference over a weak reference? We tackle these questions in this episode.
7:33
Strong reference cycles negatively impact your application's performance. They lead to memory leaks and unexpected behavior that is often hard to debug. In this episode, I show you how to resolve the strong reference cycles we created in the previous episode of this series.
7:05
In the previous installment of this series, you learned about Automatic Reference Counting and how it helps keep memory management in check. Remember that a class instance is deallocated if no properties, constants, or variables hold a strong reference to the class instance. I didn't explain what a strong reference is, though.
11:30
Before we can discuss Automatic Reference Counting, ARC for short, you need to understand the difference between value types and reference types.
Should outlets be declared weak or strong? It’s a question that pops up surprisingly frequently. In this tutorial, I’d like to definitively answer this question. I also explain the why of the answer.