<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><br></div><div>this shall apply to methods as well, why not.</div><div><br></div><div>personally i'd put things like capture list (and even parameters/result in case of closures) outside of the brackets.</div><div><br></div><div>> At present, the programer has no choice but to select a closure, even if the use case would make a local function more expressive or easier to read.<br></div><div><br></div><div>this quote raises a general question: are closures harder to read and if so can we do anything to improve their readability.</div><div><br></div><div>Mike<br></div><div><br></div></div><br></div></div>