<div dir="ltr">Hi Evan,<div>The "proposal status" page I made was just merged into master, so the place to go is now <a href="http://apple.github.io/swift-evolution/" target="_blank">http://apple.github.io/swift-evolution/</a> . This replaces the schedule document. Since your proposal was listed in the schedule under "Merged proposals that are out of scope for Swift 3.0, but will be scheduled when it is done", I put it under the "Deferred" section of the new status page.</div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Mon, Jul 18, 2016 at 12:22 PM, Evan Maloney <span dir="ltr"><<a href="mailto:emaloney@gilt.com" target="_blank">emaloney@gilt.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div>Thanks for the tip, Jacob. Unfortunately, the "schedule" document is a 404 for me, and if I search for "<a href="http://schedule.md" target="_blank">schedule.md</a>" in the repo, nothing comes up. Is the schedule document private somehow? Perhaps something that only the core team can see?</div><div><div><div><br></div><div><br></div><br><div><blockquote type="cite"><div>On Jul 15, 2016, at 7:15 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" target="_blank">jtbandes@gmail.com</a>> wrote:</div><br><div><div dir="ltr">In the "schedule" document, this proposal is listed under the section entitled "Merged proposals that are out of scope for Swift 3.0, but will be scheduled when it is done".<div><br></div><div><a href="https://github.com/apple/swift-evolution/blob/master/schedule.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/schedule.md</a><br></div><div><a href="https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d" target="_blank">https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d</a><br></div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Fri, Jul 15, 2016 at 12:32 PM, Evan Maloney via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">Hello,<div><br></div><div>Back in April, <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md" target="_blank">a proposal PR of mine</a> (<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md" target="_blank">SE-0079</a>) was merged into master that would make the following code legal when in a block where self is weak:</div><div><br></div><div><pre style="font-family:Consolas,"Liberation Mono",Menlo,Courier,monospace;margin-top:0px;margin-bottom:0px;line-height:1.45;word-wrap:normal;padding:16px;overflow:auto;border-radius:3px;color:rgb(51,51,51);background-color:rgb(247,247,247)"> <span style="color:rgb(167,29,93)">guard</span> <span style="color:rgb(167,29,93)">let</span> <span style="color:rgb(167,29,93)">self</span> <span style="color:rgb(167,29,93)">=</span> <span style="color:rgb(167,29,93)">self</span> <span style="color:rgb(167,29,93)">else</span> { <span style="color:rgb(167,29,93)">return</span> }
</pre></div><div><br></div><div>and:</div><div><br></div><div><pre style="font-family:Consolas,"Liberation Mono",Menlo,Courier,monospace;margin-top:0px;margin-bottom:0px;line-height:1.45;word-wrap:normal;padding:16px;overflow:auto;border-radius:3px;background-color:rgb(247,247,247)"><pre style="color:rgb(51,51,51);font-family:Consolas,"Liberation Mono",Menlo,Courier,monospace;margin-top:0px;margin-bottom:0px;line-height:1.45;word-wrap:normal;padding:16px;overflow:auto;border-radius:3px"> <span style="color:rgb(167,29,93)">if</span> <span style="color:rgb(167,29,93)">let</span> <span style="color:rgb(167,29,93)">self</span> <span style="color:rgb(167,29,93)">=</span> <span style="color:rgb(167,29,93)">self</span> {
<span style="color:rgb(150,152,150)">// ...code...</span></pre></pre></div><div><br></div><div>Since then, the proposal has been Awaiting Review.</div><div><br></div><div><div>Because it was a relatively minor and non-controversial change, I had assumed it would go through review somewhat quickly. Now we're getting to the cutoff for Swift 3 and I'm getting the sense that it will not be considered.</div></div><div><br></div><div>I'm sure I'm not the only proposal author who thinks it would be great to have a better sense of the selection criteria for review and some visibility into when a given proposal might come up for review.</div><div><br></div><div><div>I understand how busy the core team is, and therefore I don't mind waiting. But if, for example, there is a "review queue", I'm sure the community would benefit from knowing what's in the pipeline and what sort of proposals are of more immediate interest to the core team. At the very least, it would make the waiting easier.</div></div><div><br></div><div>What do you think?</div><div><br></div><div>And, while I have your attention, is there any chance this proposal can be considered in time for Swift 3? ;-)</div><div><br></div><div>Have a good weekend,</div><div>Evan</div><div><br></div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div></div>
</div></blockquote></div><br></div></div></div></blockquote></div><br></div></div>