How a subtle memory leak in UIViewRepresentable can silently retain your Coordinator

A developer discovered a memory leak in SwiftUI's UIViewRepresentable when assigning an instance method reference directly to a UIKit view's closure property. Passing context.coordinator.handleTap to a button's onTap closure causes the closure to strongly retain the Coordinator object, preventing it from being deallocated. Because UIViewRepresentable is a struct, the usual [weak self] Swift pattern does not apply, requiring developers to instead weakly capture the Coordinator explicitly using [weak coordinator = context.coordinator]. The recommended fix involves both a weak capture in the closure and implementing dismantleUIView to nil out the callback when SwiftUI tears down the view. This distinction is important because the Coordinator, not the struct wrapper, is the reference-type object managing UIKit-style lifetime and callback behavior.