Also, when I did the Swift 2.0 migration, we were stalled a lot by waiting for dependencies to update first. We should start a list of dependencies such that we can mark when they support 3.0 and know when we can reliably upgrade.
Also, we are currently quite far behind with our usage of AFNetworking. When they migrate to Swift 3.0 we are going to have to upgrade. We should probably start thinking about that now. On 21 March 2016 at 15:06, Stefan Arentz <sare...@mozilla.com> wrote: > TL;DR I created a swift-3.0 branch this weekend. But don’t go there yet. > It is bad. > > > With Xcode 7.3 you can install alternative toolchains. So I grabbed the > Swift 3.0 .pkg from swift.org and tried to compile a few dependencies > first. > > Flashback to Swift 1.2 migration: lots of code that does not compile > anymore. Library changes. Method signature changes. Compiler bugs. > Incorrect error messages. Compiler crashes. Swift 3.0 is in a really bad > shape right now. > > So ignore the branch. I think WWDC 16 will most likely be the time when > Apple releases Xcode 8.0 beta with some stable Swift 3.0 support. > > :fire: > > S. > > _______________________________________________ > mobile-firefox-dev mailing list > mobile-firefox-dev@mozilla.org > https://mail.mozilla.org/listinfo/mobile-firefox-dev >
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
