Re: [swift-evolution] [swift-dev] Endgame for Swift 3

> On 15 Jul 2016, at 19:46, Ted Kremenek via swift-dev > wrote: > > Hi everyone, > > Swift 3 has shaped up to be a remarkable release — a product of the > inspiration, ideas, and hard labor many people from across the Swift open > source community. It is now time,

Re: [swift-evolution] [swift-dev] Endgame for Swift 3

> On Jul 15, 2016, at 10:35 PM, Patrick Pijnappel via swift-dev > wrote: > > Isn't half of this done, or something? I seem to remember seeing code about > it, and I think there may even be a hidden switch to enable what is there. > > The parsing code seems to be in

Re: [swift-evolution] [swift-dev] Endgame for Swift 3

> > Isn't half of this done, or something? I seem to remember seeing code > about it, and I think there may even be a hidden switch to enable what is > there. The parsing code seems to be in place, toggled by the flag Context.LangOpts. EnableProtocolTypealiases:

Re: [swift-evolution] [swift-dev] Endgame for Swift 3

https://github.com/apple/swift-evolution/tree/master/proposals/0092-typealiases-in-protocols.md Isn't half of this done, or something? I seem to remember seeing code about it, and I think there may even be a hidden switch to enable what is there. Sent from my new Email

Re: [swift-evolution] [swift-dev] Endgame for Swift 3

on Fri Jul 15 2016, Dmitri Gribenko wrote: > On Fri, Jul 15, 2016 at 11:44 AM, Ted kremenek via swift-dev > wrote: >> Good question. >> >> Dave/Dmitri: do you have a recommendation here? I can see either the JIRA >> issues referencing the

Re: [swift-evolution] [swift-dev] Endgame for Swift 3

On Fri, Jul 15, 2016 at 11:44 AM, Ted kremenek via swift-dev wrote: > Good question. > > Dave/Dmitri: do you have a recommendation here? I can see either the JIRA > issues referencing the proposal (if one exists) or updating the gist. I > prefer the former. Updating the