On May 16, 2016, at 10:38 AM, Goffredo Marocchi <[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?
We’ll start discussing post-3.0 releases in August. Until Swift 3 is really wound down, it is almost impossible to make forward looking plans. -Chris > > Sent from my iPhone > >> On 16 May 2016, at 17:43, Chris Lattner via swift-evolution >> <[email protected]> wrote: >> >> >>> On May 16, 2016, at 9:29 AM, David Sweeris <[email protected]> wrote: >>> >>> >>>> On May 16, 2016, at 10:18 AM, Chris Lattner via swift-evolution >>>> <[email protected]> wrote: >>>> >>>> That said, it is also clear at this point that some of the loftier goals >>>> that we started out with aren’t going to fit into the release - including >>>> some of the most important generics features needed in order to lock down >>>> the ABI of the standard library. As such, the generics and ABI stability >>>> goals will roll into a future release of Swift, where I expect them to be >>>> the *highest* priority features to get done. >>> >>> Oh, good! I was getting worried about that. Are there any particular topics >>> that we should drop or discuss? >> >> The highest priority to me is to get the “little syntactic stuff” done that >> we want to nail down because it affects source stability. A recent thing >> that came up was @noescape -> @nonescaping and whether to make it the >> default, for example. >> >> As for dropping, it is pretty clear that we are out of time for large-scope >> additions. >> >> -Chris >> _______________________________________________ >> swift-evolution mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
