by olenhad on 9/14/16, 2:16 AM with 91 comments
by tveita on 9/14/16, 3:08 PM
https://github.com/apple/swift-corelibs-foundation/blob/mast... says they intend it to be part of Swift 3.0, but https://github.com/apple/swift-corelibs-foundation/blob/mast... still lists a lot of classes as "Incomplete" or "Unimplemented"
by thomasahle on 9/14/16, 10:42 AM
Not that I mind though. This kind of thing should be easy to auto refactor.
by hellofunk on 9/14/16, 2:22 PM
if foo == 1 && bar ==2 //normal, from other languages
if let somevar = foo, let anothervar = bar //note, must use a comma rather than &&
if case .someEnum = foobar //cannot use == !
That latter would be much easier to think about like foobar == .someEnum but it gets mucked up.
I don't understand why these can't be streamlined into something like this:
if let a = b && let d == f && foobar == .someEnum //you can't do any of this
Instead, you have to use "where" and commas rather than && in some places, the whole thing is a much greater cognitive overload than it should be for such a fundamental task in any language.
by nicky0 on 9/14/16, 10:56 AM
by WoodenChair on 9/14/16, 2:09 PM
by mark_l_watson on 9/14/16, 1:55 PM
I am surprised they don't support the latest Ubuntu with official binaries?
by dep_b on 9/14/16, 1:11 PM
Funny thing is I downloaded one of the first if not the first beta of Xcode 8 and it already migrated my projects flawlessly (where possible). It's all the other stuff that's broken.
by justsaysmthng on 9/14/16, 2:02 PM
I've already spent all day fixing, updating, searching around for all kinds of errors that the build system throws at me. It also required me to update the project dependencies to their latest versions which support swift 3/xcode 8. Some dependencies (like SwiftBond 5) have changed a lot and now my project has hundreds of syntax errors due to renamed methods, not that hard to fix, but not sure if they'll still run the same...
So this is a major upgrade to your project - do it when you have spare time to waste.
In the meantime, I'm thinking of reverting to Xcode 7.3 and running the two versions side by side... Is that possible ?
by valarauca1 on 9/14/16, 9:27 AM
by sswezey on 9/14/16, 2:28 PM
If Swift really wants to become successful, they need to work on bigger picture things like fixing breaking regressions, planning full reflection, built-in async instead of bikeshedding about array methods. I understand they want a non-breaking API from 3.0, but everyone isn't always going to be happy; and changing small functions for the vocal minority is not the correct path forward.
A list of 3.0 regressions: https://bugs.swift.org/browse/SR-2603?jql=labels%20%3D%203.0... Flatten rename proposal: https://github.com/apple/swift-evolution/blob/master/proposa...
by insulanian on 9/14/16, 7:47 AM
This created havoc in Python. Hopefully it won't happen here.
by awzurn on 9/14/16, 1:57 PM
... then again, seeing some actual refactor support in Xcode would be pretty great too, but you can't wish for too much at once.
by leshow on 9/14/16, 1:52 PM
by overcast on 9/14/16, 1:14 PM
by prit91 on 9/14/16, 3:15 PM
by skybrian on 9/14/16, 3:52 PM
by antiquark on 9/15/16, 12:40 AM
by andrewvijay on 9/14/16, 9:34 AM
by unknowingone on 9/14/16, 2:13 PM
by jinmingjian on 9/14/16, 8:26 AM
by fit2rule on 9/14/16, 11:04 AM