Swiftweekly.github.io: [125] Issue #125 - January 10, 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.

[BasThomas]

Skipping the December 27 issue; we'll be back in 2019!

[fassko]

https://github.com/apple/sourcekit-lsp/pull/24

_{Sent with GitHawk}

[fassko]

https://ericasadun.com/2018/12/12/the-beauty-of-swift-5-string-interpolation/

Some cool examples what we can do with Swift 5 String Interpolation

_{Sent with GitHawk}

[BasThomas]

https://twitter.com/AirspeedSwift/status/1073436531166048256

This is a post about really exciting new direction for Swift, using compile-time evaluation of Swift code for faster logging using string interpolation.

https://forums.swift.org/t/improving-os-log-using-custom-string-interpolation-and-compile-time-interpretation/18799

[fassko]

239 in review https://github.com/apple/swift-evolution/blob/master/proposals/0239-codable-range.md https://forums.swift.org/t/se-0239-add-codable-conformance-to-range-types/18794

_{Sent with GitHawk}

[fassko]

https://forums.swift.org/t/progress-apple-swift-docker-repo-is-up/18785

In previous issue I didn't write about this, but here is also a post in forums.

[fassko]

https://github.com/apple/swift-evolution/pull/915

This proposal is now going to be run through a review. I will merge and patch up the document for review.

Given the updates @airspeedswift and @moiseev have done on this proposal as well, I think it makes sense to add them as proposal authors as well to address any questions related to technical concerns and data compatibility issues.

[BasThomas]

You already posted that one ;)

[BasThomas]

https://twitter.com/Catfish_Man/status/1073029180508463105?s=20

_{Sent with GitHawk}

[fassko]

https://forums.swift.org/t/server-logging-api/18834

Almost all production server software needs logging that works with a variety of packages. So, there have been a number of different ecosystems (e.g. Vapor, Kitura, Perfect, ...) that came up with their own solutions for logging, tracing, metrics, etc.
The SSWG however aims to provide a number of packages that can be shared across within the whole Swift on Server ecosystem so we need some amount of standardisation. Because different applications have different requirements on what logging should exactly do, we're proposing to establish a SSWG logging API that can be implemented by various logging backends (called LogHandler).

_{Sent with GitHawk}

[fassko]

One of the most popular library has completely rewritten using Swift features like Codable. Also removing what @mattt thought would be in Swift language:

Previous versions of Alamofire's documentation introduced users to making requests with the Alamofire.request() API. This dates back to version 1 and I think it reflects Mattt's belief that Swift would gain qualified module references, allowing users to refer to modules that weren't imported by just using the module name. This never came to pass, so this API was actually misleading.

https://forums.swift.org/t/alamofire-5-one-year-in-the-making-now-in-beta/18865

I'm not sure if this can make it's way to newsletter, but quite big milestone for this popular library.

[fassko]

Good blog post by @khanlou about analyzing complexity.

The takeaway here for me is that profiling and optimizing is hard. While complexity analysis can seem a bit academic — “When am I going to use this in my real career?” one asks — understanding the time and space complexity of your algorithms can help you decide which directions to explore. In this case, understanding the time complexity of sorting led us towards a broad idea which bore fruit. Finally, benchmarking and profiling with a wide variety of data leads to the most accurate information about how your code will work in production.

And also, next time you see a sort followed by a prefix, think about replacing it with smallest(_: by:).

[BasThomas]

https://twitter.com/pathofshrines/status/1074382960420368384 + thread +
https://boats.gitlab.io/blog/post/rust-2019/

[fassko]

https://forums.swift.org/t/dec-13th-2018/18883

SSWG December 13th, 2018 meeting

Topics discussed:

• Docker
• Logging
• HTTP Client
• Postgres Client
• Prometheus

[fassko]

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

[Name lookup] Enable shadowing for type lookup and of the Swift module

Swift 5's Result type won't cause source breakages with existing uses of user-defined Result types. Amazing. 😍 https://github.com/apple/swift/pull/21370

_{Sent with GitHawk}

[fassko]

Maybe fun one

https://twitter.com/jckarter/status/1075156018198265856

[fassko]

RFC: Building Swift Packages in build-script

We want to be able to build, test and install SwiftPM packages along with the rest of the Swift toolchain. This needs to build and run using the just-built compiler, package manager and corelibs for a variety of reasons.

https://forums.swift.org/t/rfc-building-swift-packages-in-build-script/18920

[fassko]

[Proposal] Ordered collection diffing

https://github.com/apple/swift-evolution/pull/968

https://forums.swift.org/t/ordered-collection-diffing/18933

....

Let's see how far this goes.

[fassko]

Pitch: Strengthen Requirements for Synthesizing Decodable by @stephencelis

https://forums.swift.org/t/pitch-strengthen-requirements-for-synthesizing-decodable/18977

[fassko]

Improved zip API proposal pitch

https://forums.swift.org/t/improved-zip-api/18949

[fassko]

https://ericasadun.com/2018/12/26/swift-5-gives-us-nice-things-custom-string-delimiters/

_{Sent with GitHawk}

[fassko]

Great article by @twostraws how to use Result type in Swift 5 https://www.hackingwithswift.com/articles/161/how-to-use-result-in-swift

_{Sent with GitHawk}

[fassko]

Pitch about "Swift should allow for suppression of warnings, especially those that come from Objective-C" It has some valid points and lot of exploration has been done.

https://forums.swift.org/t/pitch-swift-should-allow-for-suppression-of-warnings-especially-those-that-come-from-objective-c/19216

[tjeerdintveen]

I'd like to share my in-depth article about protocols https://swiftindepth.com/2019-01-01/reasoning-about-protocols

[fassko]

https://twitter.com/jckarter/status/1081311811469598720

https://forums.swift.org/t/windows-nightlies/19174

Swift running on Windows

[fassko]

Another great articles about String interpolation https://www.hackingwithswift.com/articles/163/how-to-use-custom-string-interpolation-in-swift from @twostraws

_{Sent with GitHawk}

[BasThomas]

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

[fassko]

SwiftNIO Redis Client https://forums.swift.org/t/swiftnio-redis-client/19325

This package includes two modules: NIORedis and Redis, which provide clients that handle connection to, authorizing, and executing commands against a Redis server.

NIORedis provides channel handlers for encoding / decoding between Swift native types and Redis' Serialization Protocol (RESP).

Redis is an abstraction layer that wraps NIORedis to be callback based with DispatchQueue.

[fassko]

https://github.com/apple/swift-evolution/pull/973 by @dennisvennink

Bug SR-5754

This proposal addresses the absence of lazy versions of some Sequence-related operations by adding new types, method overloads and conditional conformances to LazySequenceProtocol on applicable types that conform to Sequence

[fassko]

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

First SSWG proposal

_{Sent with GitHawk}

[jpsim]

https://twitter.com/xge_apple/status/1083251230204260353

Exposing parser details as C API allows Swift clients, such as SwiftSyntax, to reuse compiler logics in-process. Outcomes? Significant performance gain for syntax tree generation by avoiding any forms of cross-process serialization 🙌

[BasThomas]

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

Missing members are now diagnosed via the new diagnostics framework - a big step forward https://github.com/apple/swift/pull/21756

[theblixguy]

Fixed this 2 year old bug: https://github.com/apple/swift/pull/21621

• Explanation: If T is an enum or a struct, containing a case or a static property named none, then assigning .none to a variable of type T? would cause it to have the value Optional.none rather than T.none.

  Example:

  enum Foo {
    case none
  }
  
  let test: Foo? = .none // Assigned Optional.none instead of Foo.none
  let isEqual: Bool = test == Foo.none // false
  

[BasThomas]

Awesome stuff @theblixguy!

[BasThomas]

Thanks all for helping out on this one!