When proposing changes to #SwiftLang every time you think “It’s okay, we’ll write a migrator to handle the changes automatically”, remember
it’s not actually true for production code, because the underlying compiler isn't reliable enough in the face of type errors. SEG11 all over
The migrator relies on the compiler, the compiler relies on valid types, migration causes invalid types, migration is broken.
Also, it’s killing Xcode. Thought it was supposed to be isolated from SourceKitServer? Strongly leaning towards abandoning Swift 3 branch…
and continuing to build with Xcode 7 & Swift 2.x until at least Swift 3.1. Maybe even trashing 3 branch &re-migrating from 2.x from scratch
Seems like everyone’s rushing stuff through for Swift 3.0, even though seems like future 3.x’s (3.1 etc) will still have breaking changes
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.