| Newsletter | https://swiftevolution.substack.com |
| Website | https://www.fline.dev/tag/swift-evolution-monthly/ |
| RSS Feed | https://www.fline.dev/tag/swift-evolution-monthly/rss |
🐛 Debug String.Index like a pro!
#Swift 6.1 brings clearer String.Index descriptions. Out with cryptic _rawBits, in with readable position info.
More updates 👉 https://www.fline.dev/swift-evolution-monthly-may-november-2024/
#SwiftLang #iOSDev #debugging
🔍 #Swift tightens up member import visibility!
No more surprise extensions from transitive imports. Explicit imports required for extension methods – just like types.
Full story 👉 https://www.fline.dev/swift-evolution-monthly-may-november-2024/
#SwiftLang #Swift #iOSDev
⚙️ #Swift compiler warnings are getting way more flexible!
New granular controls let you choose which warnings become errors. Perfect for large codebases and gradual upgrades.
Read more 👉 https://www.fline.dev/swift-evolution-monthly-may-november-2024/
#Swift #SwiftLang #iOSDev
🎯 The little things matter: Trailing commas everywhere in #Swift!
Function params, tuples, conditional statements – all get trailing comma support. Your git diffs just got way cleaner.
Details here 👉 https://www.fline.dev/swift-evolution-monthly-may-november-2024/
#SwiftLang #iOSDev #coding
🔑 Swift is getting smarter with Metatype Keypaths!
Finally accessing static properties in keypaths will be possible. SwiftData & database folks, this one's for you – no more workarounds needed.
Check it out 👉 https://www.fline.dev/swift-evolution-monthly-may-november-2024/
#SwiftDev #SwiftUI #SwiftLang
📱 Swift Evolution: Objective-C implementations in Swift is here!
Now you can implement Obj-C headers directly in Swift while keeping full compatibility. Perfect for modernizing legacy iOS apps without breaking things.
More details 👉 https://www.fline.dev/swift-evolution-monthly-may-november-2024/
#Swift #iOS #SwiftLang
It’s really coming – “SE-0413: Typed throws” has been accepted! 🥳
https://forums.swift.org/t/accepted-se-0413-typed-throws/69099
We will soon be able to explicitly specify the error type a function can potentially throw. This will improve the discoverability & clarity of failure cases, making error handling easier!
Hey folks, The review of SE-0413: Typed throws ran from November 16th through December 7th. SE-0413 has been accepted. Most of the major questions about the proposal were worked out during the pitch phase, and review focused on a few remaining details: Parentheses A number of people expressed that they did not like the throws(CatError) syntax, and either suggested alternatives to the parentheses or questioned if they were needed at all. The parentheses resolve a number of possible ambiguitie...
