Issue #71 25 May 2017
Written by: Jesse Squires
Things have certainly been more quiet than usual as we approach WWDC. Discussions on the mailing lists (and even Twitter!) have been sparse. Only two proposals are awaiting or actively in review and it’s unlikely we’ll see any more proposals for Swift 4.
Interested in sponsoring Swift Weekly Brief? Learn more here.
- SR-4949: No error for using
aspatterns with CoreFoundation types
- SR-4824: Add tests to check
Collectionconstraints are being enforced
- SR-4595: Tests generate lots of warnings
Episode 12: Swift Evolution
We debate if Swift evolution is pulling its weight, and if it’s possible for Swift to remain “open” without the cost.
News and community
Erica Sadun wrote about 5 Easy Dispatch Tricks in Swift. There are some great tips here to improve your experience with Swift Dispatch.
David Owens released and is continuing development on a Swift implementation of the Language Server Protocol spec. Find it on GitHub.
Commits and pull requests
George Karpenkov added support for the
-sanitize=fuzzer flag. Similarly to Clang, the flag enables coverage instrumentation, and links
libLLVMFuzzer.a to the produced binary. You can learn more about LLVM’s libFuzzer on the LLVM blog and at the libFuzzer docs. Pretty cool!
Dave Abrahams added substring comparison benchmarks.
Not new, but just recently merged, Johannes Weiß added support to statically build corelibs-foundation.
No updates on proposals this week! Check the status page for details.
It might be hard to believe but not much has happened on swift-evolution or the other lists this week. I’m starting to worry about what I’m going to write for next week’s issue! 😅
And finally — WWDC is approaching. Goats to stay calm.