> Ironically, Swift’s attempts to prevent incorrect code actually make it harder to write correct code
Yes, and strict concurrency deserves a post on itself. I wonder how NSCopyObject works with actor isolation?
Yes, and strict concurrency deserves a post on itself. I wonder how NSCopyObject works with actor isolation?
Like the post says, it’s not always clear if you’re working with a class which inherits from NSCopyObject, so how does one “break out” of strict concurrency to copy an object like this?
But yes, you do have to live with the history of the platform you're developing for. Opportunities to break backwards-compatibility are few and far-between, because users don't like when OS updates make their apps stop working.