<head></head><body>* What is your evaluation of the proposal?<div><div>Yes, seems like a great addition. I have wanted a method like this quite a few times.</div><div><br></div>* Is the problem being addressed significant enough to warrant a change to Swift?</div><div><div>Yes, I think it adds an essential part to Sequence.</div><div><br></div>* Does this proposal fit well with the feel and direction of Swift?</div><div><div>Yes, it’s surprising it wasn’t there already; it feels a very natural addition.</div><div><br></div>* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</div><div><div>.find() is the name I have seen elsewhere, and this proposed functionality is the same.</div><div><br></div>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</div><div><div>A quick reading, and had followed some earlier discussion.</div><br><!-- <signature> --><b>Patrick Smith</b><br><!-- </signature> --></div><div class="gmail_quote">
On Apr 29 2016, at 4:11 am, Chris Lattner via swift-evolution <swift-evolution@swift.org> wrote:
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p>Hello Swift community,</p>
<p>The review of "SE-0032: Add find method to SequenceType" begins now and runs through May 3. The proposal is available here:</p>
<p>https://github.com/apple/swift-evolution/blob/master/proposals/0032-sequencetype-find.md</p>
<p>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at</p>
<p>https://lists.swift.org/mailman/listinfo/swift-evolution</p>
<p>or, if you would like to keep your feedback private, directly to the review manager.</p>
<p>What goes into a review?</p>
<p>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:</p>
<p>* 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?</p>
<p>More information about the Swift evolution process is available at</p>
<p>https://github.com/apple/swift-evolution/blob/master/process.md</p>
<p>Thank you,</p>
<p>-Chris Lattner<br>Review Manager</p>
<p><br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution</p>
</blockquote>
</div></body>