Swiftweekly.github.io: [108] Issue #108 - May 3, 2018

Created on 20 Apr 2018  路  17Comments  路  Source: SwiftWeekly/swiftweekly.github.io

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.

full issue notes

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

All 17 comments

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

211 in review

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jonniedarko picture jonniedarko  路  3Comments

jessesquires picture jessesquires  路  10Comments

jessesquires picture jessesquires  路  9Comments

jessesquires picture jessesquires  路  10Comments

gregheo picture gregheo  路  3Comments