Swift 3.1 Released
swift.org
Swift 3.1 Released
1–10 of 71 posts
Re: Swift 3.1 Released
#2A week or two ago I updated a fairly large project to 3.1. Not as painful as the 3.0 upgrade by any means, but there were still a fair few warnings about features that will be deprecated in future releases. Dropping support for the initialize() function was probably one of the most prominent.
To me that seems like a nice way of doing it - warning developers about approaching changes with a fairly strong warning message, and allowing time for those changes to take place.
Re: Swift 3.1 Released
#3Hopefully it has support for warnings when formatting strings with optional values:
http://stackoverflow.com/questions/42045139/i-want-a-compile...
Re: Swift 3.1 Released
#4Hopefully it has support for warnings when formatting strings with optional values: http://stackoverflow.com/questions/42045139/i-want-a-compile...
Good news - it does. For me, it fixed a lot of bugs that I had no idea existed.
Seems like a pretty easy mistake to make, since third party libraries I use were littered with exactly the same mistake.
Re: Swift 3.1 Released
#5Just installed, compiling a fairly large project gives me "Command failed due to signal: Illegal instruction: 4" without any further information. Smooth...
Re: Swift 3.1 Released
#6Just installed, compiling a fairly large project gives me "Command failed due to signal: Illegal instruction: 4" without any further information. Smooth...
Congratulations, you managed to crash the compiler. Can you please file a bug?
Re: Swift 3.1 Released
#7Just installed, compiling a fairly large project gives me "Command failed due to signal: Illegal instruction: 4" without any further information. Smooth...
Congratulations, you managed to crash the compiler. Can you please file a bug? https://swift.org/contributing/#reporting-bugs
Of course, just did. Very surprised that this happens for a 'source compatible' point release of Swift. Especially as this can be triggered with only five fairly simple lines of code. Not good.
Re: Swift 3.1 Released
#8Hopefully it has support for warnings when formatting strings with optional values: http://stackoverflow.com/questions/42045139/i-want-a-compile...
Good news - it does. For me, it fixed a lot of bugs that I had no idea existed. Seems like a pretty easy mistake to make, since third party libraries I use were littered with exactly the same mistake.
Yep it was a really nasty one. Because it used to work differently in Swift 2.x where it would not put Optional() around it in certain circumstances.
Re: Swift 3.1 Released
#9Earlier quoted context omitted.
Congratulations, you managed to crash the compiler. Can you please file a bug? https://swift.org/contributing/#reporting-bugs
Of course, just did. Very surprised that this happens for a 'source compatible' point release of Swift. Especially as this can be triggered with only five fairly simple lines of code. Not good.
Thank you!
Re: Swift 3.1 Released
#10Earlier quoted context omitted.
Congratulations, you managed to crash the compiler. Can you please file a bug? https://swift.org/contributing/#reporting-bugs
Of course, just did. Very surprised that this happens for a 'source compatible' point release of Swift. Especially as this can be triggered with only five fairly simple lines of code. Not good.
Well they are called bugs and they exist in every software. It's not like they did it on purpose.