Unfinished concurrency story with missing synchronization primitives

6/10 Medium

The concurrency system lacks essential features like non-reentrant actor support, proper send support for actors in distributed systems, and missing primitives like Semaphore alternatives. Developers resort to Task Semaphore and various workarounds.

Swift
Category
architecture
Workaround
hack
Stage
build
Freshness
persistent
Scope
language
Upstream
open
Recurring
Yes
Buyer Type
team
Maintainer
slow

Sources

Collection History

Query: “What are the most common pain points with Swift for developers in 2025?”4/4/2026

The Concurrency story is a bit unfinished, e.g. non-reentrant actor support and `send` support for Actors (including in the distributed case)... the lack of them lead to various more-or-less ugly workarounds currently.

Created: 4/4/2026Updated: 4/4/2026