<div dir="ltr">Some previous discussion in "Pitch: @autoreleasepool attribute for loops":<div><div><br></div></div><div><a href="http://comments.gmane.org/gmane.comp.lang.swift.evolution/2796">http://comments.gmane.org/gmane.comp.lang.swift.evolution/2796</a></div><div class="gmail_extra">
<br><div class="gmail_quote">On Wed, Feb 17, 2016 at 3:05 PM, Brent Royal-Gordon 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> I often get “return blind” when looking at a method with blocks inside of it. I don’t know whether a return returns from the method or a block within that method. It would be nice to have a totally different keyword for blocks so I could distinguish the two.<br>
<br>
</span>Without endorsing the idea, I'll suggest the `leave` keyword for this role.<br>
<br>
Of course, this also kind of suggests that we ought to support non-local returns, which I don't think is realistic.<br>
<br>
(Hmm. *Could* we support non-local returns from @noescape closures passed to rethrows functions?)<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Brent Royal-Gordon<br>
Architechies<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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>
</div></div></blockquote></div><br></div></div>