<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thanks for the tip, Jacob. Unfortunately, the "schedule" document is a 404 for me, and if I search for "schedule.md" in the repo, nothing comes up. Is the schedule document private somehow? Perhaps something that only the core team can see?</div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 15, 2016, at 7:15 PM, Jacob Bandes-Storch &lt;<a href="mailto:jtbandes@gmail.com" class="">jtbandes@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">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 class=""><br class=""></div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/schedule.md" class="">https://github.com/apple/swift-evolution/blob/master/schedule.md</a><br class=""></div><div class=""><a href="https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d" class="">https://github.com/apple/swift-evolution/commit/ea5632a800444c26dbff4e20432745702732f17d</a><br class=""></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class="">Jacob<br class=""></div></div></div></div>
<br class=""><div class="gmail_quote">On Fri, Jul 15, 2016 at 12:32 PM, Evan Maloney via swift-evolution <span dir="ltr" class="">&lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt;</span> wrote:<br class=""><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" class="">Hello,<div class=""><br class=""></div><div class="">Back in April,&nbsp;<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md" target="_blank" class="">a proposal PR of mine</a>&nbsp;(<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md" target="_blank" class="">SE-0079</a>) was merged into master that would make the following code legal when in a block where self is weak:</div><div class=""><br class=""></div><div class=""><pre style="font-family:Consolas,&quot;Liberation Mono&quot;,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)" class="">    <span style="color:rgb(167,29,93)" class="">guard</span> <span style="color:rgb(167,29,93)" class="">let</span> <span style="color:rgb(167,29,93)" class="">self</span> <span style="color:rgb(167,29,93)" class="">=</span> <span style="color:rgb(167,29,93)" class="">self</span> <span style="color:rgb(167,29,93)" class="">else</span> { <span style="color:rgb(167,29,93)" class="">return</span> }
</pre></div><div class=""><br class=""></div><div class="">and:</div><div class=""><br class=""></div><div class=""><pre style="font-family:Consolas,&quot;Liberation Mono&quot;,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)" class=""><pre style="color:rgb(51,51,51);font-family:Consolas,&quot;Liberation Mono&quot;,Menlo,Courier,monospace;margin-top:0px;margin-bottom:0px;line-height:1.45;word-wrap:normal;padding:16px;overflow:auto;border-radius:3px" class="">    <span style="color:rgb(167,29,93)" class="">if</span> <span style="color:rgb(167,29,93)" class="">let</span> <span style="color:rgb(167,29,93)" class="">self</span> <span style="color:rgb(167,29,93)" class="">=</span> <span style="color:rgb(167,29,93)" class="">self</span> {
       &nbsp;<span style="color:rgb(150,152,150)" class="">// ...code...</span></pre></pre></div><div class=""><br class=""></div><div class="">Since then, the proposal has been Awaiting Review.</div><div class=""><br class=""></div><div class=""><div class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class=""><div class="">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 class=""><br class=""></div><div class="">What do you think?</div><div class=""><br class=""></div><div class="">And, while I have your attention, is there any chance this proposal can be considered in time for Swift 3? ;-)</div><div class=""><br class=""></div><div class="">Have a good weekend,</div><div class="">Evan</div><div class=""><br class=""></div></div><br class="">_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
</div></blockquote></div><br class=""></body></html>