<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="">Oh, and I just realized I have been responding to the wrong thread.<div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="" style="font-family: Palatino-Roman;"><div class=""><font face="Menlo" class="">[weak self]</font></div></div><div class="" style="font-family: Palatino-Roman;"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="" style="word-wrap: break-word;"><div class=""><font face="Menlo" class="">guard reconstitute self else { return }</font></div></div></div></div></div></div><div class="" style="font-family: Palatino-Roman;"><br class=""></div><div class="" style="font-family: Palatino-Roman;">I thought it might be handy to control how the <font face="Menlo" class="">guard</font> exits scope, enabling <font face="Menlo" class="">self == nil</font> (as well as any other reconstitutions of a <font face="Menlo" class="">weak</font> variable) failure cases to do reporting, <font face="Menlo" class="">fatalError</font>-ing, etc. I think it's important to defer to the programmer on how the weak self condition is handled, enabling any clean-up action to be taken as well as deciding whether to terminate the app, recover, etc.</div><div class="" style="font-family: Palatino-Roman;"><br class=""></div><div class="" style="font-family: Palatino-Roman;">-- E, off to pick up kids</div><div class="" style="font-family: Palatino-Roman;"><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 12, 2016, at 3:46 PM, Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">Alternatives Considered<br class=""><br class="">Status Quo<br class=""><br class="">Closures with an Optional Return Type<br class=""><br class="">Closures with a Bool Return Type<br class=""><br class="">Closures with Arbitrary Return Types<br class=""></blockquote><br class="">I would also discuss the alternative of allowing `self` to be shadowed so that you could write `guard let self = self else { return }`. Your proposal still has some advantages over that one, but I would like to see those explicitly called out and discussed.<br class=""><br class="">-- <br class="">Brent Royal-Gordon<br class="">Architechies<br class=""><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="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>