Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Swift 3.0 Released

swift.org

Post reply on HN
Print view View original

51–60 of 95 posts

Re: Swift 3.0 Released

#51

Post by anmilo »

dep_b wrote: post #39

Swift 3.0 is really nice but I backtracked out of Xcode 8.0 for now. I am used to Xcode but this one still vomits Apple internal debug messages into the console, that's really too rough for me. I'll wait for the .01 or the .1 before upgrading all my projects. 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 othe…

there's a settings flag you can add to stop those internal debug messages, which I believe started in the XCode 8 Beta. It is pretty annoying that this not clearly mentioned or toggle-able in the UI

https://twitter.com/rustyshelf/status/775505191160328194

Re: Swift 3.0 Released

#54

Post by atemerev »

awzurn wrote: post #49

Can't wait for the day when they're done deciding to only make major releases every year, and actually settle on a common syntax and platform for the language, will be great not having to worry about my source code blowing up... ... then again, seeing some actual refactor support in Xcode would be pretty great too, but you can't wish for too much at once.

AppCode delivers fantastic refactoring support. $20 per month is not that expensive, and licenses for open source development are free.

Re: Swift 3.0 Released

#55

Post by fit2rule »

sgt wrote: post #34
fit2rule wrote: post #26

Holding off on learning much more Swift for now, until things stabilize and stuff stops breaking. Its not much fun to go back to learn some Swift only to discover things have changed since last time ..

No need to hold off - now is actually the time to start learning Swift, as it's taking off. If you've written existing code, it will take you minor effort to translate the code (in most cases) and you can also use the code migrator tool.

Yeah, I guess with 3.0 it is time to dust off the ol' ~/hak/swift/ dir and see what it'll take to bring previous hacks forward ..

Re: Swift 3.0 Released

#56

Post by mrsteveman1 »

justsaysmthng wrote: post #50

If you're thinking of updating to Xcode 8, hoping that your project will 'just build', don't get your hopes too high. 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 pr…

> In the meantime, I'm thinking of reverting to Xcode 7.3 and running the two versions side by side... Is that possible ?

I think you're probably better off just keeping Xcode 8 by itself, but use Swift 2.3 for projects if you need to. There are very very few differences between 2.2 and 2.3, converting existing code over is much faster than 2.2 -> 3.0.

Re: Swift 3.0 Released

#59

Post by hellofunk »

One thing I never understood about Swift and that I don't think is addressed in Swift 3 is the widespread inconsistency with simple 'if' statements. There are at least three incompatible ways to think about 'if' syntax in Swift:

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.

Re: Swift 3.0 Released

#60

Post by timjver »

awzurn wrote: post #49

Can't wait for the day when they're done deciding to only make major releases every year, and actually settle on a common syntax and platform for the language, will be great not having to worry about my source code blowing up... ... then again, seeing some actual refactor support in Xcode would be pretty great too, but you can't wish for too much at once.

A major release doesn't necessarily have any breaking changes. Swift 4 will contain some breaking changes for sure, but Swift 5 might not.
Post reply on HN