#swift6 — Public Fediverse posts

🚀 Swift 6.3: The latest magic trick in the never-ending quest to make tech jargon sound exciting! 🎩✨ Now with "More flexible C interope" — because who doesn't love a good half-finished word in a release note? 🙄🔧
https://www.swift.org/blog/swift-6.3-released/ #Swift6.3 #TechJargon #Excitement #CInterop #ReleaseNotes #HackerNews #ngated

🚀 Swift 6.3: The latest magic trick in the never-ending quest to make tech jargon sound exciting! 🎩✨ Now with "More flexible C interope" — because who doesn't love a good half-finished word in a release note? 🙄🔧
https://www.swift.org/blog/swift-6.3-released/ #Swift6.3 #TechJargon #Excitement #CInterop #ReleaseNotes #HackerNews #ngated

Swift 6.3

https://www.swift.org/blog/swift-6.3-released/

#HackerNews #Swift6.3 #SwiftProgramming #SoftwareDevelopment #Release #Notes #HackerNews

Swift 6.3

https://www.swift.org/blog/swift-6.3-released/

#HackerNews #Swift6.3 #SwiftProgramming #SoftwareDevelopment #Release #Notes #HackerNews

Swift 6 brings six access levels for imports - but when should you use @_exported vs public import? This comparison breaks down re-exporting symbols as your own vs declaring public dependencies.

🔗: https://alexanderweiss.dev/blog/2026-01-16-exported-import-vs-public-import by Alexander Weiss (@alexanderwe)

#Swift #Swift6 #iOSDev

Overwhelmed by Swift 6 compiler settings and language modes? This breaks down which 5 settings truly matter and which you can safely ignore to cut through the complexity.

🔗: https://massicotte.org/blog/what-settings/ by Matt Massicotte (@mattiem)

#Swift6 #Swift #iOSDev #Concurrency

Seeing crashes in #CarPlay's Point Of Interest Template?
It might be surfacing because of your migration to #Swift6.
#Swift

Reported as: FB21202147

https://www.sgade.de/blog/2025-11-29-carplay-poi-mainactor-isolation/

Seeing crashes in #CarPlay's Point Of Interest Template?
It might be surfacing because of your migration to #Swift6.
#Swift

Reported as: FB21202147

https://www.sgade.de/blog/2025-11-29-carplay-poi-mainactor-isolation/

What do robot toddlers and coloring pages teach us about data races? First in a series building concrete mental models for Swift Concurrency. Feedback welcome!

https://krishna.github.io/posts/understanding-data-races-visual-guide/

#swift #concurrency #swiftconcurrency #swift6

What do robot toddlers and coloring pages teach us about data races? First in a series building concrete mental models for Swift Concurrency. Feedback welcome!

https://krishna.github.io/posts/understanding-data-races-visual-guide/

#swift #concurrency #swiftconcurrency #swift6

A few months ago, I started building CiderKit.Tween, a #Swift6 package dedicated to animation and tweening in particular.

For my fellow #Unity game devs, think DOTween but for #Swift and #SpriteKit.

Version 0.5.0 has been released with several new additions.

https://github.com/chsxf/CiderKit.Tween

#gamedev

How do you bridge the gap between legacy Apple APIs and Swift 6's strict concurrency model?

𝑀𝑎𝑖𝑛𝐴𝑐𝑡𝑜𝑟.𝑎𝑠𝑠𝑢𝑚𝑒𝐼𝑠𝑜𝑙𝑎𝑡𝑒𝑑 provides a MainActor context within synchronous methods, solving compatibility issues with APIs like 𝑁𝑆𝑇𝑒𝑥𝑡𝐴𝑡𝑡𝑎𝑐ℎ𝑚𝑒𝑛𝑡𝑉𝑖𝑒𝑤𝑃𝑟𝑜𝑣𝑖𝑑𝑒𝑟 and 𝑈𝐼𝐻𝑜𝑠𝑡𝑖𝑛𝑔𝐶𝑜𝑛𝑡𝑟𝑜𝑙𝑙𝑒𝑟. This is essential knowledge for Swift 6 migration!

🔗: https://fatbobman.com/en/posts/mainactor-assumeisolated/ by @fatbobman

#Swift6 #SwiftConcurrency #iOSDevelopment #MainActor

How do you bridge the gap between legacy Apple APIs and Swift 6's strict concurrency model?

𝑀𝑎𝑖𝑛𝐴𝑐𝑡𝑜𝑟.𝑎𝑠𝑠𝑢𝑚𝑒𝐼𝑠𝑜𝑙𝑎𝑡𝑒𝑑 provides a MainActor context within synchronous methods, solving compatibility issues with APIs like 𝑁𝑆𝑇𝑒𝑥𝑡𝐴𝑡𝑡𝑎𝑐ℎ𝑚𝑒𝑛𝑡𝑉𝑖𝑒𝑤𝑃𝑟𝑜𝑣𝑖𝑑𝑒𝑟 and 𝑈𝐼𝐻𝑜𝑠𝑡𝑖𝑛𝑔𝐶𝑜𝑛𝑡𝑟𝑜𝑙𝑙𝑒𝑟. This is essential knowledge for Swift 6 migration!

🔗: https://fatbobman.com/en/posts/mainactor-assumeisolated/ by @fatbobman

#Swift6 #SwiftConcurrency #iOSDevelopment #MainActor

🚨 BREAKING: Swift 6 introduces "typed throws" to make error handling *typesafe* and *user-friendly.* 🚨 Because, apparently, developers were just tossing random errors around like confetti at a tech conference. 🎉 Next up: Swift 7 - a guide on how to use a keyboard. 😜
https://theswiftdev.com/2025/type-safe-and-user-friendly-error-handling-in-swift-6/ #Swift6 #typedthrows #errorhandling #typesafe #userfriendly #HackerNews #ngated

🚨 BREAKING: Swift 6 introduces "typed throws" to make error handling *typesafe* and *user-friendly.* 🚨 Because, apparently, developers were just tossing random errors around like confetti at a tech conference. 🎉 Next up: Swift 7 - a guide on how to use a keyboard. 😜
https://theswiftdev.com/2025/type-safe-and-user-friendly-error-handling-in-swift-6/ #Swift6 #typedthrows #errorhandling #typesafe #userfriendly #HackerNews #ngated

Type-safe and user-friendly error handling in Swift 6

https://theswiftdev.com/2025/type-safe-and-user-friendly-error-handling-in-swift-6/

#HackerNews #TypeSafeErrorHandling #Swift6 #SwiftProgramming #UserFriendlyErrors #iOSDevelopment

Type-safe and user-friendly error handling in Swift 6

https://theswiftdev.com/2025/type-safe-and-user-friendly-error-handling-in-swift-6/

#HackerNews #TypeSafeErrorHandling #Swift6 #SwiftProgramming #UserFriendlyErrors #iOSDevelopment

Swift 6.1と6.2の主な新仕様
https://qiita.com/uhooi/items/b8f3972bf9d4bc514cb8?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #iOS #Swift #Swift6 #Swift6_1 #Swift6_2

Just released the first (early) version of a new tweening package written entirely in #swift, which supports Swift 6 Strict Concurrency:

CiderKit.Tween

Full documentation and sample project available.

More info here: https://github.com/chsxf/CiderKit.Tween

#gamedev #swift6 #ciderkit

I'm halfway through "Practical Swift Concurrency" from @donnywals , and it has already proved very useful to understand this new paradigm in concurrent multi-threaded programming.

https://practicalswiftconcurrency.com

I'm not there yet, but I'm progressing anyway.

#swift #swift6 #macdev

I'm halfway through "Practical Swift Concurrency" from @donnywals , and it has already proved very useful to understand this new paradigm in concurrent multi-threaded programming.

https://practicalswiftconcurrency.com

I'm not there yet, but I'm progressing anyway.

#swift #swift6 #macdev

Migrated one of the projects to Swift6... And fixed compatibility issues with macOS/iOS 26. Not going lie.. It was a painful experience. But I am glad that I did it. Sure migrating all other apps will be easier.

#ShellHistory #macOS26 #ios26 #Xcode26 #Swift6 #Swift #iOS #macOS #Xcode

Migrated one of the projects to Swift6... And fixed compatibility issues with macOS/iOS 26. Not going lie.. It was a painful experience. But I am glad that I did it. Sure migrating all other apps will be easier.

#ShellHistory #macOS26 #ios26 #Xcode26 #Swift6 #Swift #iOS #macOS #Xcode

#Swift #iosdev #Swift6

#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

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

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

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/

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/

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

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

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.

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/

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

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

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 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/

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/

Migrating the TelemetryDeck SDK to #Swift6: https://telemetrydeck.com/blog/migrating-to-swift-6/

Migrating the TelemetryDeck SDK to #Swift6: https://telemetrydeck.com/blog/migrating-to-swift-6/

What if I told you, Swift 6 allows you to get a compile-time guarantee that every error case is handled?

https://dandylyons.github.io/posts/typed-error-handling/

#SwiftLang #Swift6

What if I told you, Swift 6 allows you to get a compile-time guarantee that every error case is handled?

https://dandylyons.github.io/posts/typed-error-handling/

#SwiftLang #Swift6

What on earth is `@retroactive` in Swift?

Let's find out...

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

#Swift #Swift6

I am very happy to announce that AppState 2.0.0 now has support for Swift 6!

#ios #swift #macos #Swift6 #AppState #opensource #developer #swiftlang #iOSDev #watchos

https://github.com/0xLeif/AppState/releases/tag/2.0.0

I am very happy to announce that AppState 2.0.0 now has support for Swift 6!

#ios #swift #macos #Swift6 #AppState #opensource #developer #swiftlang #iOSDev #watchos

https://github.com/0xLeif/AppState/releases/tag/2.0.0

I spent the evening adding tables to SpectreKit. I found a lot of bugs in the process, but everything seems to work OK now. There is still some work to do, but I'm happy with the result. #swift #swift6