<div dir="ltr">I meant writing a proposal for having noescape be the default with an `@escaping` attribute to have different behavior. `@once` would be a separate proposal and looks to be out of scope for Swift 3.0.<div><br></div><div>The former change was mentioned by Chris Lattner in <a href="http://article.gmane.org/gmane.comp.lang.swift.evolution/16896">http://article.gmane.org/gmane.comp.lang.swift.evolution/16896</a>.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 28, 2016 at 3:21 PM, Cheyo Ximenez <span dir="ltr"><<a href="mailto:cheyo@masters3d.com" target="_blank">cheyo@masters3d.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div></div><div>Are you talking about writing a proposal for @escaping or @once after it becomes feasible? </div><div>I haven't seen a proposal for making `noescape` the default. Do you think that is with in the swift 3 scope and goal of source braking changes?</div><div><br></div><div>This is where is I saw this first. </div><div><br></div><div><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0073-noescape-once.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0073-noescape-once.md</a></div><div><div class="h5"><div><br>On May 28, 2016, at 10:18 AM, Trent Nadeau <<a href="mailto:tanadeau@gmail.com" target="_blank">tanadeau@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I agree with Jose. I especially like the idea of making `@noescape` the default with a new `@escaping` attribute. As I believed was mentioned in an earlier review, this would also make the proposed `@noescape(once)` just be `@once`. I'd be happy to write the proposal for that rename.<div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 25, 2016 at 12:43 PM, Jose Cheyo Jimenez 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"><span><br>
> * What is your evaluation of the proposal?<br>
</span>-1. noreturn is a term of art that is googable, renaming will make it obscure imo specially since it is not that common in iOS code.<br>
If the core team were to keep `noreturn` then `nonscaping` will be weird,<br>
but then if `noescape` became the default then (the non negative ;-) `escaping` would make sense.<br>
<span><br>
> * Is the problem being addressed significant enough to warrant a change to Swift?<br>
<br>
</span>no.<br>
<span><br>
> * Does this proposal fit well with the feel and direction of Swift?<br>
<br>
</span>no.<br>
<span><br>
> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
<br>
</span>n/a<br>
<span><br>
> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
</span>read the thread.<br>
<div><div><br>
_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature">Trent Nadeau</div>
</div></div>
</div></blockquote></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Trent Nadeau</div>
</div>