That being said, releases like this are pretty frustrating because they seem to reflect a focusing on tiny bits of sugar (can we even call them that?) instead of features that have a much more positive influence experience. Besides "better error messages" how do any of these things improve the development experience?
`map(\.name) vs map { $0.name }`. Why...?
`callAsFunction()` feels bizarre... how is `obj()` more elegant or less confusing than `obj.callAsFunction()`.
Meanwhile the Swift dev experience still has lots of annoying bugs & usability issues (though to its credit it has improved by leaps about bounds). My personal pet peeve is that sensible compiler synthesized inits[1] still have not been implemented despite requests (and proposals!) coming up again[2] and again[3] and again[4] and again[5]
Sometimes I wonder if anyone is actually asking questions like "what value is this providing to the user?". Maybe there's so many strong opinions nothing of substance can get through the approval process?
Announcements like this[6] get me excited that the language is heading in the right direction, but it'll be a lot more convincing when the a release shows that.
[1] https://github.com/apple/swift-evolution/blob/master/proposa...
[2] https://forums.swift.org/t/it-should-be-possible-to-generate...
[3] https://forums.swift.org/t/explicit-memberwise-initializers/...
[4] https://forums.swift.org/t/default-struct-initializer-intern...
[5] https://stackoverflow.com/questions/26224693/how-can-i-make-...