home.social

#swift6 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #swift6, aggregated by home.social.

  1. 🚀 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? 🙄🔧
    swift.org/blog/swift-6.3-relea #Swift6.3 #TechJargon #Excitement #CInterop #ReleaseNotes #HackerNews #ngated

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

    Reported as: FB21202147

    sgade.de/blog/2025-11-29-carpl

  3. 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!

    krishna.github.io/posts/unders

    #swift #concurrency #swiftconcurrency #swift6

  4. 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.

    github.com/chsxf/CiderKit.Tween

    #gamedev

  5. 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.

    github.com/chsxf/CiderKit.Tween

    #gamedev

  6. 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!

    🔗: fatbobman.com/en/posts/mainact by @fatbobman

    #Swift6 #SwiftConcurrency #iOSDevelopment #MainActor

  7. 🚨 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. 😜
    theswiftdev.com/2025/type-safe #Swift6 #typedthrows #errorhandling #typesafe #userfriendly #HackerNews #ngated

  8. 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: github.com/chsxf/CiderKit.Tween

    #gamedev #swift6 #ciderkit

  9. 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: github.com/chsxf/CiderKit.Tween

    #gamedev #swift6 #ciderkit

  10. 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.

    practicalswiftconcurrency.com

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

    #swift #swift6 #macdev

  11. 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

  12. 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
    apfeltalk.de/magazin/news/swif
    #News #Tellerrand #Apple #Coding #EntwicklerTools #IOS17 #iPad #Mac #MacOSSonoma #ProgrammierenLernen #Swift6 #SwiftPlaygrounds #Xcode16

  13. @polpielladev Good overview!
    There is so much good stuff in #SwiftTesting :
    Grouping and sub-grouping tests by suites, parameterized tests, adding traits like bug tracker links (!!) for context, disabling tests temporarily with ‘withKnownIssue’, …
    But my favorite feature is the check for specific error types and cases. This in combination with typed throws in #Swift6 🤯

  14. 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

  15. 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. 🤦‍♂️
    hackingwithswift.com/articles/ #Swift6.2 #SwiftUpdates #CodingFun #InteractiveContent #DeveloperHumor #HackerNews #ngated

  16. 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
    fline.dev/swift-6-typed-throws

  17. 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

  18. 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.

  19. 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.

  20. 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

    dandylyons.github.io/posts/pos

  21. 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

    docs.google.com/spreadsheets/d

  22. 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.

    github.com/patriksvensson/luce

  23. 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:
    dandylyons.github.io/posts/swi

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

    dandylyons.github.io/posts/typ

    #SwiftLang #Swift6

  25. 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

  26. Taking a look into AVFoundation changes in developer.apple.com/documentat
    Mostly are swift concurrency annotations. But hundreds.
    I just spot new metrics classes, which look like a replacement for access and error logs (indeed there is a session explaining it developer.apple.com/wwdc24/101)

    So, just to note how big swift 6 impact is.
    Apple needed a year bandwidth in a core framework like this.

    #AVFoundation #wwdc24 #swift6 #hls

  27. 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

  28. 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