Swift by Sundell

1. Article · Aug 30, 2026

   Why Swift is introducing a warning for weak captures within nested closures (opens the original)

   Excerpt · Neutral tone

   Read excerpt

   New in Swift 6.4 (which at the time of writing is in beta as part of Xcode 27) 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

   Feedback

2. Article · Jul 31, 2026

   Swift protocols and the main actor (opens the original)

   Excerpt

   Read excerpt

   In Swift, the @MainActor attribute can be used to associate a given type, function, or value with the global main actor, which essentially makes any such code operate on the enclosing app’s main thread. That’s incredibly useful for things like UI-related code, since UI updates (whether done using UIKit, SwiftUI, or another framework) most often need to be performed on the main thread. But how does all of this work when it comes to declaring and adopting protocols?The main actor as a requirementJ

   Feedback

Last 90 days. Choose a month to open its work.

Named in the text we hold. One piece can cover several.

• Swift2 pieces
• ExportService1 piece
• UIKit1 piece
• UI1 piece
• this:actor ExportService1 piece
• func logScanningDidStart1 piece
• error:Actor '1 piece