<div dir="ltr">On 28 October 2017 at 23:45, Mike Kluev <span dir="ltr"><<a href="mailto:mike.kluev@gmail.com" target="_blank">mike.kluev@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">on Date: Fri, 27 Oct 2017 15:15:15 -0400 Alex Lynch <<a href="mailto:lynch.sft@gmail.com" target="_blank">lynch.sft@gmail.com</a>> wrote:</div><div class="gmail_quote"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
I use local functions heavily in my day-to-day workflow and an very<br>
interested in them supporting capture lists.<br>
Here is a draft feature specification:<br>
<a href="https://bitbucket.org/snippets/lynchrb/r487zn" rel="noreferrer" target="_blank">https://bitbucket.org/snippets<wbr>/lynchrb/r487zn</a><br>
<br>
Anyone see any weak spots?<br></blockquote></div></div></div></blockquote><div><br></div><div>following C tradition to have declarations mimicking usage, the weak/unowned specifier shall be on the left to the name, as the "self" itself is on the left: self.foo</div><div><br></div><div>maybe a too wild idea, but how about this:</div><div><br></div><div>weak func foo() {</div><div> ...</div><div>}</div><div><br></div><div>as a special case of "weak self" specifier. instead of:</div><div><br></div><div>func foo() { [weak self] in</div><div> ...</div><div>}</div><div><br></div><div>of course it doesn't address everything that can be achieved by general capture list specifiers.</div><div><br></div><div>Mike</div><div><br></div></div></div></div>