For me, the challenge isn’t writing my own code that conforms to strict concurrency checking. That’s relatively easy. It is the interfacing with Apple’s own legacy frameworks that have not yet been refactored to support Swift concurrency. I’ve spent countless hours figuring out work-arounds to interface with Apple’s own preconcurrency frameworks. Sometimes it is relatively easy (if not altogether obvious), but sometimes is it a nightmare. IMHO, they should not have imposed this on us until all the standard frameworks had this sorted out.
I will stay away from Swift 6 and that strict concurrency stuff as long as I can. It’s just too painful and is a waste of too much time for no particular reason. Still hope that some sane person from the Swift designers team will realize how awful it is and will at least make it fully optional. The chances are slim though… 😫
For me, the challenge isn’t writing my own code that conforms to strict concurrency checking. That’s relatively easy. It is the interfacing with Apple’s own legacy frameworks that have not yet been refactored to support Swift concurrency. I’ve spent countless hours figuring out work-arounds to interface with Apple’s own preconcurrency frameworks. Sometimes it is relatively easy (if not altogether obvious), but sometimes is it a nightmare. IMHO, they should not have imposed this on us until all the standard frameworks had this sorted out.
I will stay away from Swift 6 and that strict concurrency stuff as long as I can. It’s just too painful and is a waste of too much time for no particular reason. Still hope that some sane person from the Swift designers team will realize how awful it is and will at least make it fully optional. The chances are slim though… 😫