@mattiem @cocoaphony The error disappears with (among other possible workarounds) prefixing the CoreData import with @-preconcurrency, however that feels like a cop-out. What's your gut take here: are we (Apple platform devs generally) facing a medium-term future where there are lots of valid "correct” API usages that, because they cannot be checked as valid and correct by the Swift concurrency checker, will permanently require manually suppressing and working around these warnings and errors?
=> More informations about this toot | View the thread | More toots from jaredsinclair@mastodon.social
=> View mattiem@mastodon.social profile | View cocoaphony@mastodon.social profile
text/geminiThis content has been proxied by September (ba2dc).