Skip to content

Comment on Has Swift's concurrency model gone too far?

Comments

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.
AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.