from Hacker News

Has Swift's concurrency model gone too far?

by pkos98 on 1/30/25, 3:03 PM with 1 comments

• by pkos98 on 1/30/25, 3:07 PM

  From the thread:

    @discardableResult
    public init(priority: TaskPriority? = nil,
        operation: sending @escaping @isolated(any) () async -> Success)
  

  > Take just the operation argument. It's a closure that is sending, escaping, declares any isolation (I don't understand this part very well yet), it's async and it returns Success. That's a whole bunch of facts - 7 to be precise - you need to know about just one parameter of this constructor. I understand that all 7 make sense and there's nothing you can do about it within the current strict concurrency model.