Is adding a `Sendable` requirement a breaking change?

[haikuty]

Thanks for the reply.

@hborla

This is only a problem if there is no possible way to address a warning. For libraries that have not yet been updated to include concurrency annotations, @preconcurrency is designed to suppress diagnostics in client projects,

Is this from the discussion of SE-0337 still accurate?

@Douglas_Gregor

The intent behind Swift 6 is that it will not silently accept the presence of a potential data race (without unsafe code explicitly involved somewhere), so @preconcurrency must not completely silence the diagnostics. Hence, they'll be warnings in Swift 6.

(sorry I haven't checked, I've been out for an extended period).