4 ms·

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

• Zikes 12y ago
  After 1.0 API changes really should increment the major version.
  • ebbv 12y ago
    Unless you say "We're probably going to break things." when you announce it, which they did.
    • cozzyd 12y ago
      Perhaps they should have chosen a more appropriate version number then.
      • zwily 12y ago
        Apple doesn't claim to do semver
        • Zikes 12y ago
          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.