TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Has Swift's concurrency model gone too far?

2 pointsby pkos984 months ago

1 comment

pkos984 months ago
From the thread:<p><pre><code> @discardableResult public init(priority: TaskPriority? = nil, operation: sending @escaping @isolated(any) () async -&gt; Success) </code></pre> &gt; Take just the operation argument. It&#x27;s a closure that is sending, escaping, declares any isolation (I don&#x27;t understand this part very well yet), it&#x27;s async and it returns Success. That&#x27;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&#x27;s nothing you can do about it within the current strict concurrency model.