<div dir="ltr">+1 from me. I have been caught out :(<div><br></div><div>I would go further and make all captured variables read only unless marked by inout, i.e.:</div><div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">func example(inout x: Int) { <br> escape { _ = x } // OK, immutable capture<br> noEscape { _ = x } // OK, immutable capture<br> noEscape {[inout x] in _ = x } // OK, closure is @noescape<br> escape {[inout x] in _ = x } // error: closure cannot implicitly capture an inout parameter unless @noescape<br>}</blockquote><div><br></div><div>Which would make closures consistent with functions.</div><div><br></div><div>Even though I would go further it is still a +1 for me for this proposal since it is a step in the right direction.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"> -- Howard.<br></div></div>
<br><div class="gmail_quote">On 17 February 2016 at 12:30, Chris Lattner 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">Hello Swift community,<br>
<br>
The review of "Limiting inout capture to @noescape contexts" begins now and runs through February 19th. The proposal is available here:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0035-limit-inout-capture.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0035-limit-inout-capture.md</a><br>
<br>
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<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>
or, if you would like to keep your feedback private, directly to the review manager.<br>
<br>
<br>
What goes into a review?<br>
<br>
The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br>
<br>
* What is your evaluation of the proposal?<br>
* Is the problem being addressed significant enough to warrant a change to Swift?<br>
* Does this proposal fit well with the feel and direction of Swift?<br>
* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
More information about the Swift evolution process is available at<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br>
<br>
Thank you,<br>
<br>
-Chris Lattner<br>
Review Manager<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>