[147] Issue #147 - November 7, 2019

[BasThomas]

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]

🐣 I'd love feedback on a pitch for some useful new Collection operations: https://forums.swift.org/t/pitch-add-rangeset-and-related-collection-operations/29961 Feel free to respond here, in the forums, or via DM!

https://twitter.com/nnnnnnnn/status/1187443017264877568

[fassko]

Adding support for Windows as a Platform

I've been making progress on Windows support for SPM, and one of the things I'd like to add now is adding Windows as a supported platform in the Package Description. Since would change the public API, I wanted to check in if anyone thought this would need a proposal or had any opinions, or if it was small enough to do without.

https://forums.swift.org/t/adding-support-for-windows-as-a-platform/30158

[BasThomas]

Finally https://twitter.com/daniel_dunbar/status/1187827740650672128

[BasThomas]

🐣 I'd love feedback on a pitch for some useful new Collection operations:

Already in the last issue 😄

[fassko]

Pre-Pitch Codable Customization using PropertyWrappers

I recently released v1.0 of CodableWrappers (posted here) if you would like to discuss the library). It's features seem possibly worth writing my first Pitch, so I'd like to gauge the interest level in a more fleshed out pitch and if so, discuss how it would work in Swift (or probably the standard library).

https://forums.swift.org/t/pre-pitch-codable-customization-using-propertywrappers/30244

[fassko]

Announcing CodableWrappers

I'd like to announce version 1.0.0 of a library I'm calling CodableWrappers.

It uses Property Wrappers to greatly simplify non-default serialization of Codable Types. Check out the Readme or blog post for more information, but I'll give a quick overview here as well.

https://forums.swift.org/t/announcing-codablewrappers/30242

[fassko]

Multi-Pattern and Conditionally Compiled Catch Clauses

Currently, each catch clause in a do-catch statement may only contain a single pattern and where clause, and may not be conditionally compiled using a #if directive. This is inconsistent with the behavior of cases in switch statements which provide similar functionality. It also makes some error handling patterns awkward to express. This proposal extends the grammar of catch clauses to support #if and a comma-separated list of patterns (with optional where clauses), resolving this inconsistency.

Swift-evolution thread: Thread

[fassko]

https://diamantidis.github.io/2019/10/27/swift-nio-server-in-an-ios-app

_{Sent with GitHawk}

[fassko]

Starter task

SR-11677 [Compiler] Offer a better diagnostic when && is used in trailing where clause declaration

[fassko]

Officially supported MongoDB Driver

I work on our driver for Swift, MongoSwift. My team (@mbroadst, @patrick) and I would like to pitch the driver to SSWG and the community for consideration.

We’re currently working on adding an asynchronous SwiftNIO-based version of our API to meet the SSWG incubation process minimal requirements. This is still in the design phase, and we’d love to hear feedback from the community on what we’ve come up with so far.

https://forums.swift.org/t/officially-supported-mongodb-driver/30324

[fassko]

Starter task

SR-11679 [Compiler] Incorrect fixit suggestion for init in CFType extension

[BasThomas]

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

[BasThomas]

https://swift.org/blog/sswg-update/

[irshadpc]

https://nshipster.com/device-identifiers/

[BasThomas]

https://nshipster.com/device-identifiers/

Hm, does this have anything to do with Swift.org and its open source projects? It's a great blog post; I'm just not sure if it would fit in this one :)

[BasThomas]

269 in review

[fassko]

GitHub / Swift Package Management Service

I head up the Package Registry project at GitHub and we're putting together a pitch for how the package registry service will work. I'd love to gather your ideas and concerns so I can incorporate those areas into the coming pitch.

Our goal is to present a package management service specification which could be implemented by anyone, not only GitHub. This spec will include necessary API endpoints, package naming (URL spec), versioning system, and other elements required or in addition to the basics. We plan to open source our implementation (written in Go) such that others can contribute back to it and progress can be made in the open.

https://forums.swift.org/t/github-swift-package-management-service/30406/5

[fassko]

https://twitter.com/Lukasaoz/status/1189835893106003969

_{Sent with GitHawk}

[BasThomas]

https://github.com/apple/swift-package-manager/pull/2397

[theblixguy]

Those two starter tasks have already been picked up by someone else, so I think it shouldn’t be included in the newsletter

[ebelinski]

I would like to propose adding a new website I launched called Swiftly. I would suggest adding a blurb like:

Eugene Belinski announced Swiftly, an example-driven Swift reference website.

Or a bit more verbosely:

Eugene Belinski announced Swiftly, an example-driven Swift 5.1 reference website for developers of all levels.

[BasThomas]

https://spec.fm/podcasts/swift-unwrapped/311779

[BasThomas]

267 accepted https://forums.swift.org/t/accepted-se-0267-where-clauses-on-contextually-generic-declarations/30474

[fassko]

Swift 5.2 branching date re-scheduled for December 9th

Upon review, it appears that the original branching schedule was overly conservative and put the branch date significantly earlier than necessary for convergence. In order to reduce cherry-picking and branch maintenance, we are pushing our branch date for Swift 5.2 to December 9.

https://forums.swift.org/t/swift-5-2-branching-date-re-scheduled-for-december-9th/30478

[fassko]

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

_{Sent with GitHawk}

[fassko]

The latest #AppleOSS project: #ServiceTalk, a framework for service-to-service communication, built using @netty_project, featuring improved usability and new features https://servicetalk.io

https://twitter.com/davelester/status/1192148300234772482

_{Sent with GitHawk}

[fassko]

[Returned for revision] SE-0265: Offset-Based Access to Indices, Elements, and Slices

This review ended on October 21st, but because of the LLVM conference, the Core Team didn't have an opportunity to discuss it until last week.

https://forums.swift.org/t/returned-for-revision-se-0265-offset-based-access-to-indices-elements-and-slices/30503

_{Sent with GitHawk}

[jpsim]

What does ServiceTalk have to do with Swift? @fassko

[fassko]

What does ServiceTalk have to do with Swift? @fassko

It helps Server side, but yeah I agree let’s leave it out.

[BasThomas]

Which is why I opted not to add it when I came across it. :)