[swift-evolution] Isolated and failable green threads?
brent at architechies.com
Thu Jan 28 02:31:10 CST 2016
> There are two concepts from Erlang that I really like:
> - threads are very light-weight ([green threads]), and memory cannot be accessed accross threads (isolated threads)
> - when a thread dies, the entire app doesn't crash, but the nearest [supervisor] cleans up and can re-launch a new thread
> Applying this to apps written in Swift, I would expect would lead to
> - fewer app crashes
> - developers become more likely to architecture their app by using the [actor model]
> I am sure these ideas are not new here, but I couldn't find a discussion on it by searching the archive. What are your thoughts on bringing isolated green threads that are allowed to crash to Swift?
Mainly, that concurrency is out of scope for Swift 3 (https://github.com/apple/swift-evolution/blob/master/README.md#out-of-scope). Hang in there, though. :^)
More information about the swift-evolution