<div dir="ltr">Perhaps this is something where we could have a few compiler options to handle different preferences.<div><br></div><div>You could have options like:</div><div> * -Wexplicit-owner-capture (for explicit self)</div><div> * -Wexplicit-capture (for explicit non-trivial references)</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 9, 2015 at 10:15 AM, Kevin Ballard <span dir="ltr"><<a href="mailto:kevin@sb.org" target="_blank">kevin@sb.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div><span class=""><div>On Tue, Dec 8, 2015, at 02:57 PM, Andrew Bennett wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div>Kevin, I think you should definitely propose that (weak in outer and inner closure), it's one of the surprises that led me to this proposal. I also really like your suggesting of requiring explicit weak/strong on self, I think this could solve many cases.<br></div>
</div>
</blockquote><div> </div>
</span><div>I submitted the proposal as <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001134.html" target="_blank">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001134.html</a> (unfortunately it looks like the plain text version got garbled :/).<br></div>
<div> </div>
<div>Regarding explicit weak/strong, my feeling is it would probably get too annoying to have to type `[self] in` everywhere. But it may be worth playing with.<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">
<div> </div>
<div>-Kevin Ballard</div>
</font></span></div>
</blockquote></div><br></div>