4 ms·
A good read on the future of Swift concurrency is this from Chris Lattner, https://gist.github.com/lattner/31ed37682ef1576b16bca1432ea9f782 https://gist.github.
by aplummer 9y ago
A good read on the future of Swift concurrency is this from Chris Lattner, https://gist.github.com/lattner/31ed37682ef1576b16bca1432ea9f782 https://gist.github.com/lattner/31ed37682ef1576b16bca1432ea9.... I think currently still slated for Swift 5
- bsaul 9y agoThis is going to be very interesting to watch. They decided to add concurrency after having built an extraordinary complex language. Something people like rob pike thought would be very hard to do (and as both a go and a swift coder, i must say i tend to think he's probably got a point).
- gilgoomesh 9y agoThe concurrency model was planned before the first betas but has been delayed. The devs always knew how they wanted concurrency to work.
- bsaul 9y agoI didn't know that, but i'm not surprised because chris lattner clearly knows what he's doing. I'm still curious to see how it ends up integrating in a language that's been evolving a lot since its design. Saying that they managed to keep concurrency orthogonal to the rest of the language means Rob Pike was "wrong" (or at least what i understood from his point). However, after reading the conversations around the async proposal, it seems to me on the contrary that it is very tightly related to other parts (such as error throwing mechanism, GCD library and syntax in general). We'll see. I wish i didn't have the feeling swift core team is understaffed, because at least for iOS development it is really a joy to program with.