Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Has Swift's concurrency model gone too far? (swift.org)
2 points by pkos98 11 months ago | hide | past | favorite | 1 comment


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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: