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/dgregor79/status/987173055909715968
We found a bit of a footgun in Swift with non-escaping closures and Objective-C interoperability. It's got me worried, and I'd like to hear opinions on our options: https://forums.swift.org/t/implicit-escaping-of-closures-via-objective-c/12025
https://twitter.com/AirspeedSwift/status/987393939001917440
Random number API proposal for Swift has been accepted!
https://forums.swift.org/t/accepted-se-020-random-unification/12040
count(where:) proposal: https://github.com/apple/swift-evolution/pull/840
https://twitter.com/twostraws/status/988499714835451905
Finding it hard to keep up with all the changes in #swiftlang? I made a new site just for you: https://www.whatsnewinswift.com https://twitter.com/twostraws/status/988499714835451905/photo/1
207 accepted with revisions: https://forums.swift.org/t/se-0207-add-a-containsonly-algorithm-to-sequence/11686/102
211 in review
Tensor flow docs: https://github.com/tensorflow/swift
Specifically in the Swift for TensorFlow docs, there's the "Swift for TensorFlow Design Overview" section that IMO is worth specifically calling out: https://github.com/tensorflow/swift/blob/master/docs/DesignOverview.md
https://twitter.com/slava_pestov/status/990015849858662400
The great uninlining of the standard library begins - thanks @Ilseman! https://github.com/apple/swift/pull/16226
212 in review
I'll get a draft up tomorrow 馃憤
https://twitter.com/slava_pestov/status/991148638683381760
Really excited about this change: https://github.com/apple/swift/pull/16249
This lays the groundwork for finally eliminating SubstitutionList, the old representation for a mapping of generic parameters to concrete types
SubstitutionList is really just a typedef I added for ArrayRef
, a problematic representation that does no information hiding and leaves memory management to the user
https://twitter.com/slava_pestov/status/991579691399036928
I had no idea, but it turns out that exhausiveness checking for switch statements is a really hard problem. We鈥檝e made huge strides in correctness recently thanks to @CodaFi_, and now a team member is working on performance: https://github.com/apple/swift/pull/16300
Most helpful comment
Specifically in the Swift for TensorFlow docs, there's the "Swift for TensorFlow Design Overview" section that IMO is worth specifically calling out: https://github.com/tensorflow/swift/blob/master/docs/DesignOverview.md