To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.
The current draft for this issue in _drafts/. If you want to contribute directly, feel free to open a pull request.
https://twitter.com/slava_pestov/status/1037958164535078912
If we’re lucky we might soon be able to assign to ‘self’ in class convenience initializers, addressing a long-standing language restriction: https://forums.swift.org/t/allow-self-x-in-class-convenience-initializers/15924
I think a wider audience than those who keep close tabs on the forums might find this useful, so I hope to put in a plug here:
https://forums.swift.org/t/notes-on-numerics-in-swift/15746
A great number of questions are raised in these forums as to the functioning and design of numeric types and protocols in Swift. Sometimes, the answer can be found only by digging through the source code, and even then it's hard to place what you learn there within a larger context. Therefore, I've compiled a series of articles that delve into these topics in more detail.
Yes! Thanks, @xwu!
Sent with GitHawk
Swift's stable branch (v5.0) is upgrading to LLVM 7.0
https://forums.swift.org/t/stable-branch-update-tomorrow-clang-llvm-required/16142
https://speakerdeck.com/basthomas/taken-for-granted
I think @BasThomas won't add it himself so I will do it. I think it's a great presentation about Swift language history.
Ha, thanks @fassko. Will add it! 😊
https://twitter.com/SwiftLang/status/1041767756075425792
Swift 4.2 is released! Read about it here: https://swift.org/blog/swift-4-2-released/
https://twitter.com/slava_pestov/status/1041943141987713024
The constraint solver is now iterative rather than recursive — this should fix some stack overflow issues: https://github.com/apple/swift/pull/19203
What’s new in Swift 5.0 by @twostraws
https://www.hackingwithswift.com/articles/126/whats-new-in-swift-5-0
There is also a Playground.
Really cool list of Swift packages for Linux by @tib
https://theswiftdev.com/2018/09/18/swift-packages-for-linux/
https://twitter.com/slava_pestov/status/1042268507780505600
In Swift, foo.self always evaluates to foo. So naturally, .self should be a valid keypath as well: https://github.com/apple/swift/pull/19382
Now we’re just waiting for tuple keypaths so we can have full parity between member access syntax and keypath syntax
Most helpful comment
https://speakerdeck.com/basthomas/taken-for-granted
I think @BasThomas won't add it himself so I will do it. I think it's a great presentation about Swift language history.