Swiftweekly.github.io: [143] Issue #143 - September 12, 2019

[fassko]

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.

[fassko]

https://twitter.com/slava_pestov/status/1169782954173837314

Turns out it’s not much of an exaggeration to say that this tweak directly leads to the elimination of over 400 lines of code from the compiler

https://github.com/apple/swift/pull/27033

[fassko]

Differentiable Programming Mega-Proposal

We have completed a comprehensive proposal for the differentiable programming feature we’ve been incubating over the last 1.5 years. We’ve gone over many iterations on the feature design, and have partially completed the implementation. Now we are ready to start a discussion on Swift Evolution, specifically on upstreaming and standardizing the feature.

Since this proposal is overly long (~60 pages), we hope to start by merging it into the docs/ directory in apple/swift via apple/swift#27034, and draft bite-sized proposals that contain references to the mega-proposal.

https://forums.swift.org/t/differentiable-programming-mega-proposal/28547

[fassko]

We are happy to announce the opening of the development phase for Swift 5.0.4 for Linux with a planned release by the end of September 2019. The process for the dot-releases remains the same as for Swift 4.2 5.

Details

• Release manager: @kevints (kevints on GitHub)
• Merge window open: September 5, 2019 (now)
• Merge window close: September 18, 2019
• Target branches: corelibs-foundation:swift-5.0-branch and corelibs-xctest:swift-5.0-branch
• Process documentation: see announcement
• Planned release: End of September 2019

https://forums.swift.org/t/development-open-for-swift-5-0-4-for-linux/28556

[fassko]

Swift on Server Workgroup Meeting Notes 8th August

• Swift.org Blog post
• Badges shields.io
• Joannis's MongoDB driver
• Joannis's Async DNS client
• Security vulnerabilities
  .. and more

https://forums.swift.org/t/august-11th-2019/28553

[BasThomas]

263 revision

[BasThomas]

Thanks for creating the issue — you beat me to it. I'm actually planning to release this one next week to change the biweekly schedule. :)

[fassko]

I've been waiting for this day for a long time! Finally thread sanitizer (TSan) for Swift 5.1 on Linux works well enough that we can enable it in SwiftNIO's CI.

https://github.com/apple/swift-nio/pull/1130

Thanks very much to http://github.com/yln and team for making this happen!

https://twitter.com/johannesweiss/status/1169968226324897795

[jpsim]

https://twitter.com/gradle/status/1169920641559957505

The native team at Gradle is proud to announce Swift support with the following features:

🚀 Compile, link, and install applications and libraries
✨ Interoperability with C++
🥇 World-class dependency management
👀 Xcode IDE support
and more

[fassko]

Yet another varargs “splat” proposal

Forwarding variadic arguments has come up fairly often in discussion, and I thought I'd try my hand at working up a proposal, with a focus on arguments against the oft-proposed "prefix operator" syntax. Implementation forthcoming.

Latest version currently available at: https://github.com/gwynne/swift-evolution/blob/splat-proposal/proposals/NNNN-forward-array-to-variadic-args.md

https://forums.swift.org/t/yet-another-varargs-splat-proposal/28649

[fassko]

https://twitter.com/jeremyphoward/status/1171100202414923776

_{Sent with GitHawk}

[fassko]

https://github.com/apple/swift/blob/master/docs/CToSwiftNameTranslation.md

_{Sent with GitHawk}

[fassko]

https://twitter.com/johannesweiss/status/1171727059976105984

[fassko]

Generic Covariance to improve API Usage

https://forums.swift.org/t/generic-covariance-to-improve-api-usage/28719

[fassko]

Extended Error Messages

As a follow up from Future of Diagnostics UX a couple weeks back, I wanted to further explore the idea of "extended diagnostic messages" and see if they would be a good fit for Swift. What follows is a rough pitch for what that might look like. I'm not sure if this will/should result in an evolution proposal, but I think writing this up using the pitch format makes it easy to evaluate and discuss alternatives.

I'm interested in any and all feedback people have on whether they'd find this useful! I'm especially interested in hearing from anyone who has worked with Rust/Elm in the past and can comment on the benefits & drawbacks of their approaches to diagnostics.

https://forums.swift.org/t/pitch-extended-error-messages/28754

_{Sent with GitHawk}