> 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, however, to talk about the
> 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 place, toggled by the flag
>
> 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:
https://github.com/apple/swift/blo
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
(ht
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 proposal (if one exists) or updating the gist. I
>> pr
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, however, to talk about the endgame for the
release.
Here are the key points:
The last day to take planne
