[139] Issue #139 - July 25, 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]

Finally: https://twitter.com/UINT_MIN/status/1149409709968912384

[fassko]

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

_{Sent with GitHawk}

[BasThomas]

https://twitter.com/Ilseman/status/1149449826930528257

Non-ASCII String case-conversion benchmarks added by @armen_mkrtchian in https://github.com/apple/swift/pull/25309 uncovers optimization opportunity for ASCII strings. Optimizations landed by @Catfish_Man in https://github.com/apple/swift/pull/26007.

[BasThomas]

https://twitter.com/edd/status/1149438747609448449

Very exciting @TensorFlow community news: we're forming SIG MLIR to form a strong engineering-driven open community, with weekly open design meetings https://groups.google.com/a/tensorflow.org/d/msg/developers/8EUhHX71WL4/OHnemEdkDQAJ

[fassko]

Proposal Review: SSWG-0008 (Prometheus Client)

https://forums.swift.org/t/feedback-swift-prometheus-implementation/26928

_{Sent with GitHawk}

[fassko]

Pitch: [stdlib] Cleanup callback for fatal Swift errors

In the event of a fatal error caused by Swift code, there is no direct way to get the error message and context from Swift without out-of-process log parsing. Fatal errors "fall through" to signal handlers at which point the crash context is lost. The goal of this proposal is to provide a native Swift cleanup callback for fatal errors without the complexity of signal handlers nor allowing attempted recovery. This context could be written to disk or logged in a custom format or aggregated for later analysis.

https://forums.swift.org/t/pitch-stdlib-cleanup-callback-for-fatal-swift-errors/26977

[fassko]

[Pitch] Compilation conditions for word size

A lot of code written to support more than one platform contains #if arch() conditions to handle differences between 32-bit or 64-bit platforms or little and big endian CPUs. This may turn into long statements like #if arch(x86_64) || arch(arm64) || arch(s390x) || arch(powerpc64) || arch(powerpc64le), enumerating every (currently) supported architecture which must be handled by that #if … #endif clause.

https://forums.swift.org/t/pitch-compilation-conditions-for-word-size/26995

[fassko]

Swift Server Workgroup July 11th. 2019 meeting notes

https://forums.swift.org/t/july-11th-2019/26986

[BasThomas]

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

This is a cool thing Erik's working on to make Swift traps more user-friendly. By encoding the error message in the DWARF line table, you'll see the message in .dSYM-symbolicated backtraces and crash reports, without strings leaking in your binaries https://github.com/apple/swift/pull/25978

[fassko]

https://forums.swift.org/t/swift-5-0-2/27008

_{Sent with GitHawk}

[fassko]

Require parameter names when referencing to functions

https://forums.swift.org/t/require-parameter-names-when-referencing-to-functions/27048

[fassko]

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

SwiftNIO now has automated public API breakage checking. Thanks @tomerdoron for integrating this & @xge_apple and team for making the awesome swift-api-digester.

SwiftNIOgrowingup

The script to check API breakages should work for any SwiftPM project btw: https://github.com/apple/swift-nio/blob/master/scripts/check_no_api_breakages.sh

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

Example failing PR that deliberately removes something public: https://github.com/apple/swift-nio/pull/1072

[fassko]

LLVM monorepo transition update

https://forums.swift.org/t/llvm-monorepo-transition-update/27079

[BasThomas]

262 in review (on the 22nd)

_{Sent with GitHawk}

[fassko]

https://twitter.com/dgregor79/status/1152280218083586051

_{Sent with GitHawk}

[BasThomas]

Seems like https://forums.swift.org/t/se-0261-identifiable-protocol/26602 hasn't been mentioned before so I'll add that

[fassko]

Pitch: Standard Library Preview Package

https://forums.swift.org/t/pitch-standard-library-preview-package/27202

[fassko]

The review of SE-0262: Demangle Function begins now and runs through July 29, 2019.

https://forums.swift.org/t/se-0262-demangle-function/27199

[fassko]

https://twitter.com/wlisac/status/1153323204095561728

_{Sent with GitHawk}

[fassko]

Pitch: Requesting larger amounts of randomness from SystemRandomNumberGenerator

I propose adding a new method to SystemRandomNumberGenerator: randomBytes(count:), which will enable generating an arbitrary number of random bytes. This is a minor quality of life pitch that can provide a small but meaningful performance improvement to randomness-heavy code.

https://forums.swift.org/t/pitch-requesting-larger-amounts-of-randomness-from-systemrandomnumbergenerator/27226

[fassko]

Clarify the cryptographic properties of SystemRandomNumberGenerator

I recently proposed a patch to change the documentation of SystemRandomNumberGenerator to affirmatively state that it is cryptographically secure on all platforms, and that it will crash on any platform where it cannot provide that guarantee.

https://forums.swift.org/t/clarify-the-cryptographic-properties-of-systemrandomnumbergenerator/27249

[zntfdr]

I know it's a bit late however, in case this issue needs more content, I'd like to propose my new article on Swift 5.1 Collection Diffing for the "News and community" section.

This is my tweet about it and Scott Perry (aka @numist), the person behind the original pitch and PR, has a nice Twitter thread with even more insights and behind the scenes.

Thank you for your consideration 😃

[BasThomas]

Hey @zntfdr! It's a fantastic article — thanks for that! That said, we try to focus on those things happening in open source, not necessarily branching out to articles written about it — exceptions sometimes being made for articles on the inner workings of the code.

Thanks for letting us know about it!

[zntfdr]

Hey @zntfdr! It's a fantastic article — thanks for that! That said, we try to focus on those things happening in open source, not necessarily branching out to articles written about it — exceptions sometimes being made for articles on the inner workings of the code. ...

@BasThomas absolutely no worries, many thanks! ❤️

_{Sent with GitHawk}

[jpsim]

For what it’s worth, I thought the article was an excellent fit for this blog, explaining a swift standard library algorithm is very relevant to this blog in my opinion.