I'm working on migrating our codebase to be Xcode 16 compatible. At my company we have warnings as errors enabled, and for now we are in Swift 5 mode as we are not yet ready to adopt concurrency (we're working on it).
It seems Xcode 16 will warn you about concurrency errors even in Swift 5 mode. At the moment, they are only getting in our way. We want to get onto Xcode 16 and handle concurrency separately, but it seems Xcode 16 wants to force us to handle those two (both rather monumental) tasks at the same time.
Does the discussion in this thread seem relevant? I.e., does @preconcurrency import help you, or are you in one of the buggy cases where @preconcurrency introduces a warning (which should be fixed)?
If you can, consider making lastActionDateSortDescriptor a computed property. That way there’s no shared state, and it can be safely accessed from any isolation domain, even if NSSortDescriptor is not Sendable.
I don't love the idea of making something computed just to satisfy memory safety warnings :/ especially when I don't want to opt into said warnings to begin with
