<div dir="ltr">Well that was where I was going next, heh.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 16, 2016 at 9:41 AM, Jens Alfke <span dir="ltr"><<a href="mailto:jens@mooseyard.com" target="_blank">jens@mooseyard.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On May 16, 2016, at 9:37 AM, Nate Birkholz via swift-users <<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>> wrote:</div><br><div><span style="font-family:Alegreya-Regular;font-size:15px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I understand how @noescape works, and some of its benefits, I *think*, but if I am correct, it almost seems like it should be added automatically to my closure definitions until it becomes clear that the closure has to escape its context, much like I tend to declare variables as `let` until it becomes clear I need a `var`. </span><br></div></blockquote></div><br><div>IIRC, there is a current proposal to change the language in exactly that way — i.e. to have noescape be the default and use an attribute like “@escapes” to declare that a closure can be stored by the callee and called later.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>—Jens</div></font></span></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Nate Birkholz</div>
</div>