[interpol_p]

The recent Swift 1.2 release brought a whole load of code breaking changes. None of Swift 1.0 was explicitly deprecated.

[Sephiroth87]

That's a bit different, they explicitly said Swift is a work in progress and code compatibility is not guaranteed between versions...

[Zikes]

After 1.0 API changes really should increment the major version.

[ebbv]

Unless you say "We're probably going to break things." when you announce it, which they did.

[cozzyd]

Perhaps they should have chosen a more appropriate version number then.

[zwily]

Apple doesn't claim to do semver

[Zikes]

Regardless, that is what developers have come to expect. Not that semver is adopted wholesale, but at least don't break the API without incrementing the major version.