In this week's issue we time travel in unit tests and use protocols as UI mixins. Additionally Tuomas
|
May 2 · Issue #74 · View online |
|
Happy reading! As always, if you’d like to support Swift Weekly please share this issue with friends and colleagues.
|
|
|
What in the World is an “Escaping Closure” in Swift?
Andrew Bancroft writes about the concept of an “escaping closure” and how to handle them when developing your apps.
|
Time traveling in Swift unit tests – John Sundell – Medium
A lot of code that we write relies on the current date in some way. Whether it’s cache invalidation, handling time sensitive data, or keeping track of durations. John Sundell takes a look at how to test code that relies on dates in a simple and fun way — using “time traveling”.
|
Swift Protocols with Default Implementations as UI Mixins
Christian Tietze with a very simple way to use Swift protocols as UI mixins.
|
Using SwiftLint and Danger for Swift Best Practices
In this article Candost Dağdeviren writes about using SwiftLint and Danger to keep your codebase clean and consistent.
|
Swift range containment operator – Szy – Medium
Not everyone knows ~= operator — it’s an pattern matching operator to check whether the range on the left includes the value on right. Szy extends it in a useful way in this article.
|
Test Doubles In Swift - Marco Santarossa
A keen developer writes a lot of unit tests to cover the code to use in production. Unfortunately, a component can sometimes be difficult to test because of its dependencies, and you would be tempted to give up. Hang on, Test Doubles are what you need to make a test easy to write.
|
|
iOS Developer @ Rheinische Post
Join one of the biggest german news companies and work with us on our upcoming RP ONLINE app. For our office in Düsseldorf we are searching for a fulltime iOS developer who is passionate about creating high value and user friendly applications and wants to join the whole process, from idea through concept to the final release. German language skills required. Interested? Check our job description.
|
|
Swift with a hundred engineers | Skilled.io, the Swift Community.
Tuomas Artman shares the good and the bad from Uber’s Swift rewrite.
|
Everything a Swift Dev Ever Wanted to Know About Machine Learning
This talk presents a fast, concrete, down-to-earth survey of machine learning, from the perspective of iOS & Swift.
|
Writing Your UI Swiftly
In this talk, Sommer Panage explores how the structure and properties of the Swift Language make writing your application and UI code simpler.
|
|
Swift.org - Swift Source Compatibility Test Suite Now Available
The Swift team is pleased to announce the release of a new Swift source compatibility test
suite as part of the effort
to maintain source compatibility in future Swift releases.
|
|
GitHub - Geek-1001/Clue
Clue - Flexible bug report framework for iOS
|
GitHub - Meniny/Fire-in-Swift
Fire-in-Swift - A delightful HTTP/HTTPS networking framework for iOS/macOS/watchOS/tvOS platforms written in Swift.
|
[Constraint solver] Rework how we select the next disjunction to visit. · apple/swift@3c5b393 · GitHub
This commit by Mark Lacey to the Swift compiler reworks how the next disjunction to visit by the constraint solver is selected and could improve type checking time by 11-13%.
|
Did you enjoy this issue?
|
|
|
|
If you don't want these updates anymore, please unsubscribe here
If you were forwarded this newsletter and you like it, you can subscribe here
|
|
|