如何迁移UIControl Publisher至Swift 6并消除并发警告

针对你遇到的两个迁移问题，核心是要在遵守Main Actor调用规则的同时，确保Subscriber的访问符合Swift 6的并发安全要求，以下是具体解决方案：

问题根源解析 #

1. 第一个警告：addTarget(_:action:for:)是UIControl的Main Actor隔离方法，必须在Main Actor上下文调用，直接在非isolated的Publisher逻辑中调用会触发合规警告。
2. 第二个错误：给Publisher/Subscription添加@MainActor标记后，Subscriber可能带有自身的actor隔离属性，在Main Actor上下文直接持有并访问非Sendable的Subscriber会违反Swift 6的并发安全规则，导致跨actor发送值的错误。

正确实现方式 #

通过拆分Main Actor隔离逻辑和Subscriber的安全访问，结合AnySubscriber的Sendable特性解决问题：

import Combine
import UIKit

// 定义符合Publisher协议的UIControl包装类型
struct UIControlPublisher<Control: UIControl>: Publisher {
    typealias Output = Control
    typealias Failure = Never
    
    private let control: Control
    private let events: UIControl.Event
    
    init(control: Control, events: UIControl.Event) {
        self.control = control
        self.events = events
    }
    
    // 保持receive方法为非isolated，避免强制绑定Main Actor
    func receive<S>(subscriber: S) where S: Subscriber, Never == S.Failure, Control == S.Input {
        let subscription = UIControlSubscription(
            subscriber: AnySubscriber(subscriber),
            control: control,
            events: events
        )
        subscriber.receive(subscription: subscription)
    }
}

// 自定义Subscription，处理UIControl的事件绑定
private final class UIControlSubscription<Control: UIControl>: Subscription {
    typealias Input = Control
    typealias Failure = Never
    
    // 使用AnySubscriber（Sendable类型）存储订阅者，确保并发安全
    private let subscriber: AnySubscriber<Control, Never>
    private let control: Control
    private let events: UIControl.Event
    private var isCancelled = false
    
    init(subscriber: AnySubscriber<Control, Never>, control: Control, events: UIControl.Event) {
        self.subscriber = subscriber
        self.control = control
        self.events = events
        
        // 在Main Actor上下文添加target，解决第一个警告
        Task { @MainActor in
            control.addTarget(self, action: #selector(handleControlEvent), for: events)
        }
    }
    
    func request(_ demand: Subscribers.Demand) {}
    
    func cancel() {
        isCancelled = true
        // 在Main Actor上下文移除target
        Task { @MainActor in
            control.removeTarget(self, action: #selector(handleControlEvent), for: events)
        }
    }
    
    // UIControl事件默认在Main线程触发，直接发送值即可
    @objc private func handleControlEvent() {
        guard !isCancelled else { return }
        _ = subscriber.receive(control)
    }
}

// 扩展UIControl，提供便捷的publisher创建方法
extension UIControl {
    func publisher(for events: UIControl.Event) -> UIControlPublisher<Self> {
        UIControlPublisher(control: self, events: events)
    }
}

关键优化点 #

• Main Actor逻辑隔离：仅在调用addTarget和removeTarget时，通过Task { @MainActor in ... }切换到Main Actor上下文，避免将整个类型标记为Main Actor隔离。
• Sendable订阅者包装：使用AnySubscriber将原始Subscriber包装为Sendable类型，确保在Main Actor上下文访问时符合Swift 6的并发安全规则，解决跨actor发送值的错误。
• 取消与内存管理：通过isCancelled标记和事件移除逻辑，避免内存泄漏和无效的事件发送。

内容的提问来源于stack exchange，提问作者naljin