Not to start an argument, but I am more concerned about how we go about avoiding the Swift 3.0 issue where a bunch of accepted proposals did not make the implementation cut and were not all automatically dragged on the next release, but would have essentially to be discussed and agreed upon again. Please do tell me if I misunderstood something here, I apologise if so.
Sent from my iPhone > On 12 Nov 2016, at 08:40, Adrian Zubarev via swift-evolution > <[email protected]> wrote: > > Accepted for which release? Swift 3.1 or Swift 4.0? Thanks. > > > > -- > Adrian Zubarev > Sent with Airmail > > Am 6. Oktober 2016 um 01:19:54, Douglas Gregor via swift-evolution > ([email protected]) schrieb: > >> Proposal Link: >> https://github.com/apple/swift-evolution/blob/master/proposals/0142-associated-types-constraints.md >> >> Hello Swift Community, >> >> The review of SE-0142 "Permit where clauses to constrain associated types” >> ran from September 23…30, 2016. Feedback on this proposal was overwhelmingly >> positive. The proposal is accepted. >> >> - Doug >> >> _______________________________________________ >> 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
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
