John Sundell:

New in Swift 6.4 […] is a warning which is emitted when a nested closure performs a weak capture while the parent closure implicitly captures that object as a strong reference.

At first glance, that new diagnostic could be a bit puzzling, since it might seem unnecessary to have to specify such a weak capture twice (or, alternatively, move it to the parent closure’s capture list), but it turns out that it’s an incredibly useful new warning that can help us avoid a quite common kind of memory management bug.

[…]

Finally, in situations where capturing self strongly doesn’t actually lead to a retain cycle, we can silence the new warning for nested weak captures by explicitly adding self to the outer closure’s capture list, such as when creating a Task within the following example[…]

Previously:

• Swift 6.4
• Xcode 27 Announced
• How to Automate Memory Leak Detection With XCTest
• Avoiding Implicit Retain Cycles When Using Swift Function References
• Weak Self: Closure Rules of Thumb
• Swift “guard” Capture Specifier Pitch
• Implicit Capturing of Self in Swift 5.3
• Dealing With Weak in Closure-based Delegation
• Stop the weak-strong Swift Dance

Automatic Reference Counting (ARC) Language Design Memory Management Programming Swift Programming Language