> On May 17, 2016, at 5:35 AM, Jeremy Pereira via swift-evolution > <[email protected]> wrote: > > >> On 16 May 2016, at 18:38, Goffredo Marocchi via swift-evolution >> <[email protected]> wrote: >> >> Quite sad we could not get into ABI stability for Swift 3... but are we >> talking Swift 3.1 or 4.0? > > > Disappointing is my first thought, in fact worrying. Two years after the > language was announced, the ABI is still not stable. > > Of the original Swift 3 goals, it looks like many will not be met. There were > seven goals and only two are still in the Readme file[1]. On the assumption > that the other five were all dropped because they will not be achieved in > Swift 3, this looks like failure. > > I’ve been following the evolution list on and off since it started and it > hasn’t felt like failure. In fact, it felt like important progress has been > made and the language will be hugely better for it, but I do hope that the > development team does take the opportunity to review the release in light of > the original goals to see if there are any opportunities to improve the > development process for the next release.
https://en.wikipedia.org/wiki/Hofstadter%27s_law > [1] > https://github.com/apple/swift-evolution/blob/d6e62467b03435bdc4b3bd473c3dcffb9fdd6a71/README.md > compared to > https://github.com/apple/swift-evolution/blob/f11d2e970521f5df0f7510f89ee9c7decb3fa394/README.md -Pierre
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
