As a developer who uses Swift regularly, should be something that’s almost muscle memory to you. I’ve written about using before in the context of when you…

Donny Wals's blog offers insights into iOS development, Swift programming, and software engineering best practices. Readers can explore articles covering topics such as SwiftUI, Combine framework, and iOS app architecture patterns. Additionally, they can learn about iOS app testing, debugging techniques, and publishing apps on the App Store.

Donny Wals

Explores proper usage of [weak self] in Swift's Task-based concurrency to prevent memory leaks. Explains why immediately unwrapping weak self at the start of a Task doesn't solve memory issues, and demonstrates better approaches like unwrapping self only when needed within loops or using optional chaining. Covers the differences between completion handler patterns and Task-based async code for memory management.

How to use [weak self] in Swift Concurrency Tasks? – Donny Wals

The basics of using [weak self] in completion handlers

Using [weak self] and unwrapping it immediately in a Task

Using [weak self] in a longer running Task