Swift Around the Web
So the Swift 3.0 goal of ABI Stability has been put on hold until a future Swift release. Since I don't come from a computer science background, it's hard for me to understand what this really means. Glad to see this article from @benatbensnider actually explaining it!
"So while ABI compatibility might seem like a big deal to have been pushed off, it very likely doesn't affect the day to day of most Swift developers.
The most compelling arguments thus far have been around the fact that some developers would like to distribute libraries in binary form so as to protect intellectual property, license agreements, etc. Not having ABI compatibility is actually a legitimate concern for developers wishing to distribute binary libraries, but I don't really feel like that's a very large number of developers. Enterprises wishing to make private libraries internally available are still able to provide private Carthage repositories and/or private CocoaPods specs to host the libraries in source form, and rely on the build process to compile everything together at once. Additionally, it is currently possible to ship binary libraries, the libraries just need to be recompiled and distributed for each new breaking compiler version."
I'll be honest,
guard case and
for case still don't come very naturally to me. I always have to look them up via my own blog post, but this is a lot more advanced stuff to keep around for reference.