We're discussing a proposed redesign of the Swift Package manifest API: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170220/033151.html …
-
-
It's because too many devs break things in minor bumps because it's "not a real breaking change"
1 reply 0 retweets 1 like -
Replying to @sgrif
Yeah; we're hoping we can get package developers to actually follow semver in this ecosystem. But what we really need is... (1/2)
1 reply 0 retweets 0 likes -
(2/2) need semver enforcement, which we think is doable (at least for Swift API), but not for Swift 4.
1 reply 0 retweets 0 likes
Replying to @rballard
Having an automated tool that can tell you semver-compliance at the type level would be huge in that regard
4:23 PM - 25 Feb 2017
from Ottawa - Gatineau
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.