Hi, thanks for the video I think unowned can be useful for better comprehension of the code. For example, i will put unowned self on updateUI in the viewDidLoad, and weak self on the closure of fetchData instead. This clearly indicates what may or may not happen for a new developper on the project
Thanks for this video. I’m also not a fan of using unowned self for the reason you mentioned. It’s just too hard (and sometimes impossible) to know for sure it is safe.
Did you find this explanation useful? What are your thoughts on using [unowned self]? Let me know in the comments 🚀
Clear and on point. Good video!
Explanation ability on point✅
Nice and brief explanation! Thanks for the video.
Excellent video. Best regards from Brazil.
Hi, thanks for the video
I think unowned can be useful for better comprehension of the code.
For example, i will put unowned self on updateUI in the viewDidLoad, and weak self on the closure of fetchData instead.
This clearly indicates what may or may not happen for a new developper on the project
It’s indeed a good example of where using unowned shouldn’t be able to create a crash 👍
Thanks for this video. I’m also not a fan of using unowned self for the reason you mentioned. It’s just too hard (and sometimes impossible) to know for sure it is safe.
Possible with unit test