<div dir="ltr">IIRC, there were at least the following counter-arguments:<div>1. One must break API and ABI compatibility to add @escaping to an existing function<br><div>2. @nonescaping case is actually quite as common as @escaping</div></div><div><br></div><div>Frankly speaking, I support both of this arguments. I'll also add another counter-argument.</div><div><br></div><div>Lazy map and filter will be marked as @escaping. Now consider the following code:<br></div><div><br></div><div>func sum<T>(_ array: [T], transform: (T) -> Int) -> Int {</div><div> return array.lazy.map(func).reduce(0, combine: +)</div><div>}</div><div><br></div><div>`transform` will be marked as @escaping, despite that `transform` never actually escapes `sum`.</div><div><br></div><div>I believe that we should not accept nonescaping-by-default until we get a powerful lifetimes system, as in Rust.</div><div><br></div><div>I think it makes sense to create a mini-proposal just for renaming of @noescape to @nonescaping.</div><div><br></div><div>- Anton</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-20 20:37 GMT+03:00 Austin Zheng <span dir="ltr"><<a href="mailto:austinzheng@gmail.com" target="_blank">austinzheng@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Trent Nadeau had prepared a proposal on Chris Lattner's recommendation, and there was a discussion thread a few weeks back: <a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/19756" target="_blank">http://thread.gmane.org/gmane.comp.lang.swift.evolution/19756</a>.<div><br></div><div>Not sure what the outcome was. I don't see any open PRs to merge the proposal into the swift-evolution repo.</div><div><br></div><div>Austin</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Jun 20, 2016 at 9:06 AM, Антон Жилин <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hmm, I guess you are right, there would be no point keeping @nonescaping, then.<div><br></div><div>- Anton</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-20 18:55 GMT+03:00 David Waite <span dir="ltr"><<a href="mailto:david@alkaline-solutions.com" target="_blank">david@alkaline-solutions.com</a>></span>:<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><span><blockquote type="cite"><div>On Jun 20, 2016, at 9:39 AM, Антон Жилин via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">* Rename @noescape to @nonescaping, and make @nonescaping the default case</div></div></blockquote></span>Do you mean replace @noescape with its opposite, @escaping?</div><span><font color="#888888"><div><br></div><div>-DW</div><div><br></div></font></span></div></blockquote></div><br></div>
</div></div><br></div></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">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>
<br></blockquote></div><br></div>
</blockquote></div><br></div>