<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:13px">Isn&#39;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.</span></blockquote><div> </div>The parsing code seems to be in place, toggled by the flag <span style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre">Context.</span><span class="" style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre">LangOpts</span><span style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre">.</span><span class="" style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre">EnableProtocolTypealiases:</span><div><span class="" style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;white-space:normal"><a href="https://github.com/apple/swift/blob/master/lib/Parse/ParseDecl.cpp#L2080">https://github.com/apple/swift/blob/master/lib/Parse/ParseDecl.cpp#L2080</a></span><br></span></div><div><span class="" style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;white-space:normal"><br></span></span></div><div><span class="" style="color:rgb(51,51,51);font-family:Consolas,&#39;Liberation Mono&#39;,Menlo,Courier,monospace;font-size:12px;white-space:pre"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;white-space:normal">Is this still blocked by support elsewhere?</span></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 16, 2016 at 2:19 PM, Karl Wagner via swift-dev <span dir="ltr">&lt;<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0092-typealiases-in-protocols.md" target="_blank">https://github.com/apple/swift-evolution/tree/master/proposals/0092-typealiases-in-protocols.md</a></div><div><br></div><div>Isn&#39;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.<br><br><div style="font-family:&#39;Helvetica Neue&#39;,&#39;Helvetica&#39;,Helvetica,Arial,sans-serif;font:&#39;-apple-system-body&#39;">Sent from my new <a href="https://itunes.apple.com/app/apple-store/id922793622?pt=814382&amp;mt=8&amp;ct=my_new_email" target="_blank">Email</a></div></div></div><div><div><br><br><blockquote type="cite" style="margin:1ex 0 0 0;border-left:1px #ccc solid;padding-left:0.5ex"><div><div class="h5"><div>On Jul 15, 2016 at 7:46 PM, &lt;<a href="mailto:swift-dev@swift.org" target="_blank">Ted Kremenek via swift-dev</a>&gt; wrote:<br><br></div></div></div><div><div><div class="h5"><p style="margin-right:0px;margin-bottom:15px;margin-left:0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255);margin-top:0px!important">Hi everyone,</p><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">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.</p><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">Here are the key points:</p><ul style="margin:15px 0px;padding-left:30px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><li style="margin:0px"><p style="margin:0px 0px 15px">The last day to take planned source-breaking changes for Swift 3 is <strong style="margin-top:0px"><a dir="ltr">July 27</a></strong><a dir="ltr">.</a></p></li><li style="margin:0px"><p style="margin:0px 0px 15px">On that day, there will likely be a set of approved-but-not-implemented proposals for Swift 3 — including proposals for source-breaking changes. Will have an open discussion on that day on the fate of those unimplemented proposals in the context of Swift 3 and future Swift releases.</p></li><li style="margin:0px"><p style="margin:0px 0px 15px"><a dir="ltr">Starting on </a><strong style="margin-top:0px"><a dir="ltr">August 1</a></strong> we will open up discussion about Swift 4. Part of this discussion will likely be guided by important work that was deferred from Swift 3, as well as the a goal of achieving binary stability in Swift 4. Until then, however, discussion should remain focused on Swift 3.</p></li><li style="margin:0px"><p style="margin:0px 0px 15px">Note that there is an intentional gap of a few days between the last planned day to take source-breaking changes for Swift 3 and when we start talking about Swift 4. The idea is to provide some time for the community to take stock of where things have ended up for Swift 3.</p></li><li style="margin:0px"><p style="margin:0px 0px 15px">The final branching plan for Swift 3 development is to be determined, but the final convergence branch is likely to be cut from <code style="margin:0px 2px;padding:0px 5px;white-space:nowrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px">master</code> around that date or shortly after. Part of it comes down to the discussion <a dir="ltr">on July 27</a> on how to handle the remaining unimplemented proposals for Swift 3.</p></li><li style="margin:0px"><p style="margin:0px 0px 15px">The final release date for Swift 3 is TBD, but essentially <a dir="ltr">after July 27</a> the intent is that Swift 3 is in full convergence and not in active development.</p></li></ul><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">With these dates in mind, I want to call attention to some approved-but-not-yet-implemented proposals that currently I have nobody on Apple&#39;s Swift team able to tackle in the next couple weeks:</p><ul style="margin:15px 0px;padding-left:30px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0042-flatten-method-types.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0042: Flattening the function type of unapplied method references</a></li><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0068-universal-self.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0068: Expanding Swift <code style="margin:0px 2px;padding:0px 5px;white-space:nowrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px">Self</code> to class members and value types</a></li><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0075-import-test.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0075: Adding a Build Configuration Import Test</a></li><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0096-dynamictype.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0096: Converting dynamicType from a property to an operator</a></li><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0077-operator-precedence.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0077: Improved operator declarations</a></li><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0092-typealiases-in-protocols.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0092: Typealiases in protocols and protocol extensions</a></li><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0110-distingish-single-tuple-arg.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0110: Distinguish between single-tuple and multiple-argument function types</a></li></ul><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">Some proposals — like <a href="https://github.com/apple/swift-evolution/tree/master/proposals/0075-import-test.md" style="color:rgb(65,131,196)" target="_blank">SE-0075</a> — are things we can add at any time, but many of the others tie into the goal of achieving some degree of source-stability for Swift in Swift 3. I&#39;m letting the community know that these proposals currently have no implementation traction in case there is interest in helping make them happen in time for Swift 3.</p><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">Related, I&#39;d like to call out a special thanks to the community for getting implementation traction on SE-0095:</p><ul style="margin:15px 0px;padding-left:30px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><li style="margin:0px"><a href="https://github.com/apple/swift-evolution/tree/master/proposals/0095-any-as-existential.md" style="color:rgb(65,131,196);margin-top:0px" target="_blank">SE-0095: Replace <code style="margin:0px 2px;padding:0px 5px;white-space:nowrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px">protocol&lt;P1,P2&gt;</code> syntax with <code style="margin:0px 2px;padding:0px 5px;white-space:nowrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px">P1 &amp; P2</code> syntax</a></li></ul><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">Currently there is a <a href="https://bugs.swift.org/browse/SR-1938" style="color:rgb(65,131,196)" target="_blank">JIRA issue</a> and <a href="https://github.com/apple/swift/pull/3293" style="color:rgb(65,131,196)" target="_blank">pull request</a> tracking work on implementing this proposal.</p><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">In addition to these language proposals, there is also an assortment of outstanding work for the Standard Library that would be great to do for Swift 3. There is a gist summarizing those tasks:</p><ul style="margin:15px 0px;padding-left:30px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)"><li style="margin:0px"><a href="https://gist.github.com/gribozavr/37e811f12b27c6365fc88e6f9645634d" style="color:rgb(65,131,196);margin-top:0px" target="_blank">https://gist.github.com/gribozavr/37e811f12b27c6365fc88e6f9645634d</a></li></ul><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">These tasks are broken down in relative order of difficulty, with a JIRA issue associated with each one of them. If a JIRA isssue is currently not assigned to anyone, please consider them fair game to tackle if you are interested. API changes that have currently not gone through the evolution process will still need an evolution proposal, even if they are listed in the gist. If you take on a specific task, please assign the JIRA issue to yourself so others know it is being tackled.</p><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">Thank you to everyone — and I mean <em>everyone</em> — who has contributed to making Swift 3 happen.</p><p style="margin:15px 0px;font-family:Helvetica,arial,sans-serif;font-size:14px;background-color:rgb(255,255,255)">Ted</p></div></div>_______________________________________________
swift-dev mailing list
<a dir="ltr" href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>
<a dir="ltr" href="https://lists.swift.org/mailman/listinfo/swift-dev" target="_blank">https://lists.swift.org/mailman/listinfo/swift-dev</a>
</div></blockquote></div></div></div><br>_______________________________________________<br>
swift-dev mailing list<br>
<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-dev</a><br>
<br></blockquote></div><br></div>