I&#x27;m not sure if Swift really needs language-level concurrency support. As it stands, you can wrap any C library which provides some sort of concurrency and make it feel like native functionality because of Swift&#x27;s syntactic sugar such as trailing closures. For example, I&#x27;m a huge fan of the library Venice[0] which provides CSP by wrapping libmill (single-threaded like libuv, uses setjmp&#x2F;longjmp instead of callbacks unlike libuv), essentially providing a Go-level api without language-level support. Its what Zewo[1] is built off of, and what allows all of its api&#x27;s to be synchronous without any extra effort.<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;VeniceX&#x2F;Venice" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;VeniceX&#x2F;Venice</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;Zewo&#x2F;Zewo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Zewo&#x2F;Zewo</a>