Breaking changes in Swift 6

I don't claim to speak for the core team, but my personal opinion is that we should consider a potential small number of changes to fix quirks in the language that are actively harmful in practice, or make the language harder to learn. Examples would be cleaning up some of the implicit conversions in the type checker, or narrowing down associated type inference to make it easier to reason about and implement correctly.

I'd be nervous about opening up the release to a broader "rethinking" of anything, especially things that have in the past been controversial (access control, etc).

19 Likes