<div dir="ltr">:+1: if it is more common, perhaps even if it isn't. Although I don't think the standard library is the right place to look. I'm pretty sure if you did the same check in Dispatch you'd find the opposite case.<div><br></div><div>I think production app code is probably a better place to look, although I'm not sure of any good examples of open source swift 2 app code. It would be nice for a lot of these proposals if there was a common reference list of libraries and apps which are popular, mature, swift2 and open source so we could gauge the impact.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 20, 2015 at 7:10 AM, Matthew Johnson via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">@noescape is safer because it does not require thinking about lifetime issues for captured objects. My hunch was that @noescape (or @autoclosure with implies @noescape) is also more common. I had a look through the standard library and this is definitely the case there.<br>
<br>
What does everyone think about making @noescape the default and introducing @escaping (or something similar) to annotate function arguments that do escape the call stack?<br>
<br>
Matthew<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div>