🚀Swift 6 brings Typed Throws

Precise error handling that’s smarter, safer & faster!
🎯 No more vague `catch` blocks
🙅‍♂️ Know *exactly* what errors you’re dealing with.

📖 Read now → https://swiftshorts.com/2025/05/30/typed-throws-in-swift-6

#SwiftLang #Swift6 #iosdev

#Swift #iosdev #Swift6

Swift 6.2 is out, and just like a Hollywood sequel, it promises all the bells and whistles with none of the substance. 🎬 Same old Swift, new version number, and endless "interactive" content to convince you coding is fun! 😂 Keep "hacking" your way to the next update, because all the cool kids are doing it. 🤦‍♂️
https://www.hackingwithswift.com/articles/277/whats-new-in-swift-6-2 #Swift6.2 #SwiftUpdates #CodingFun #InteractiveContent #DeveloperHumor #HackerNews #ngated

What's New in Swift 6.2?

https://www.hackingwithswift.com/articles/277/whats-new-in-swift-6-2

#HackerNews #Swift6.2 #SwiftUpdates #Programming #News #Coding #Tips #HackingWithSwift

🤔 I am curious, what is your take on Swift 6 adaptation?

- 1️⃣ Can't be bothered
- 2️⃣ I’m still learning and adapting it to some modules
- 3️⃣ I’ve migrated all my projects to Swift 6 already

And why?

#swift #iOSdev #swift6 #ios

New article uncovering a totally underused feature in Swift 6! 📰 Read it to learn how you can vastly improve your error handling while reducing boilerplate code. Recommended for every developer, from solo Indies to large teams. Can save you hours of debugging! 🐞⏱️
#Swift #Swift6 #iOSDev #ErrorHandling
https://www.fline.dev/swift-6-typed-throws-error-chains/

At https://talk.objc.io/ I’ve found a series about Swift 6 Concurrency, see here. I’m going to read/watch the episodes since my Swift knowledge is still on Swift 5.9.
#swift #swiftlang #swiftconcurrency #swift6 #swift6concurrency
@swift

Will Swift embedded be available on ESP32-S3? #swiftembedded #swift #swift6

Spent months building an open-source framework to make Swift error handling actually enjoyable. Was really hoping to share it at try! Swift Tokyo, but my talk didn’t get selected. Now I'm thinking of turning it into a YouTube video instead. ▶️

Would anyone be genuinely interested? 👀👇
#Swift #Swift6 #ErrorHandling #TypedThrows

Swift Playgrounds: Erstes Update seit Mai 2024 veröffentlicht
Apple hat Swift Playgrounds 4.6 für Mac und iPad veröffentlicht – das erste Update seit Mai 2024. Die neue Version erfordert mindestens macOS Sonoma 14 oder iOS/iPadOS 17 und beendet die Unte
https://www.apfeltalk.de/magazin/news/swift-playgrounds-erstes-update-seit-mai-2024-veroeffentlicht/
#News #Tellerrand #Apple #Coding #EntwicklerTools #IOS17 #iPad #Mac #MacOSSonoma #ProgrammierenLernen #Swift6 #SwiftPlaygrounds #Xcode16

I commented out warn_unqualified_access attributes because they generate a bunch of warnings in #swift6 but then I get panic-inducing crashes when I forget the . in modifiers.

I updated #fedicat to #swift6 again which is not anything you should notice except it crashed intermittently last time I tried, and maybe this time's the charm.

The template code for Audio Unit Extension App in Xcode 16.1 will crash with Swift 6. It needs to treat the callback given to AUParameter.token(byAddingParameterObserver:) as nonisolated and immediately dispatch to the main thread. #swift6 #AUv3

Transitioning from #swift5 to #swift6 is difficult like any other transition. But it's even more challenging when you don't know which language mode you are currently using.

Let's learn about Swift language modes. I assure you. It's not quite as simple as you may think.

#swiftlang #iosdev #xcode #SPM

https://dandylyons.github.io/posts/post-26/am-i-using-swift-5-or-6/

There is so much counterintuitive information in the transition from #Swift5 to #Swift6 . Many people don't understand the difference between Swift tools and language modes.

Xcode, SPM, and Swift CLI all handle this slightly differently.

I'd like to crowd source some info about how Swift behaves differently depending on tools version, language mode, etc.

I would appreciate anyone willing to contribute to this spreadsheet. #swiftlang

https://docs.google.com/spreadsheets/d/15CYe85pQNmKMIEM-2jhRPu2lQJAFSorviPm3MintqR8/edit?usp=sharing

this #swift6 upgrade is telling me I should be using a functional programming language

Mkay in the end I forked all three - CoreDataEvolution, ManagedModels and PredicateKit but the result works nicely.

Reasons for forking the first two:

Mainly to replace the dependency against swift-syntax with swift-syntax-xcframework. The later is a community project attempting to provide pre-build XCFramework versions of swift-syntax and using it instead of the source package gives an unreasonable performance boost when editing or compiling in Xcode.

Reasons for forking PredicateKit:

The way ManagedModels does it's magic results in the lack of _kvcKeyPathString compatible KeyPaths for which I built a workaround that may or may not break in the future.

I could create an issue for the KeyPath-Problem with ManagedModels but my usage of it together with PredicateKit feels like too much of niece case to bother people with.

I could also create PRs but using swift-syntax-xcf also feels like a very niece case - all three forks are available in their own branches on my GitHub though.

#healsRants #healsCodes #Swift #Swift6 #CoreData

Would any #swift dev out there know if it's intentional that #xcode16 constantly re-indexes the swift-syntax package if you have a dependency on it in your Project?

In my case I'm using ManagedModels which has macros and depends on swift-syntax and every time I edit any of my source files XCode jumps into a 20+ seconds "Indexing" frenzy for swift-syntax and it's products to the extend of making code completion useless because it just doesn't pop-up and bogging down previews to a crawl.

#swiftLang #swift6 #xcodeHelp #apple #iosDev #boostAppreciated

I just open-sourced my test assertion library for #swift which I've been using in one of my projects for a while.

The new test framework in #swift6 is a significant improvement, but I was missing Shouldly from .NET too much.

https://github.com/patriksvensson/luce

I conformed an external type "Character" to Codable. In #Swift6 this is supposed to be a warning unless I explicitly mark it @retroactive. (See SE-0364).

But here I have no warning. Does anyone know why? Does this warning not appear for standard library types?

See also:
https://dandylyons.github.io/posts/swift-6-retroactive-attribute/