<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><div class=""><br class=""></div><div class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="direction: ltr;" class=""><blockquote type="cite" class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* What is your evaluation of the proposal?<br class=""></div></div></blockquote><br class=""><div style="direction: ltr;" class="">I think it is too limiting and I’d rather have find() be merged with current index() method.</div><div style="direction: ltr;" class=""><br class=""></div><div style="direction: ltr;" class="">// I believe these used to be called find() in swift 1.0</div><div style="direction: ltr;" class="">func index(of element: Self.Iterator.Element) -> Self.Index?</div><div style="direction: ltr;" class="">func index(@noescape where predicate: (Self.Iterator.Element) throws -> Bool) rethrows -> Self.Index?</div><div style="direction: ltr;" class=""><br class=""></div><div style="direction: ltr;" class="">I think it is really confusing to have an index() and a find() that do very similar things. </div><div style="direction: ltr;" class=""><br class=""></div><div style="direction: ltr;" class="">I rather have an overloaded find() </div><div style="direction: ltr;" class=""><br class=""></div><div style="direction: ltr;" class=""><div style="direction: ltr;" class="">func find(indexOf element: Self.Iterator.Element) -> Self.Index?</div><div style="direction: ltr;" class="">func find(@noescape indexOf predicate: (Self.Iterator.Element) throws -> Bool) rethrows -> Self.Index?</div></div><div style="direction: ltr;" class=""><div style="direction: ltr;" class=""><div class="">func find(@noescape element predicate: (Self.Iterator.Element) throws -> Bool) rethrows -> Self.Iterator.Element?</div><div class=""><br class=""></div></div></div><div style="direction: ltr;" class="">// Return a tuple with the index and element</div><div style="direction: ltr;" class=""><div class="">func find(@noescape predicate: (Self.Iterator.Element) throws -> Bool) rethrows -> (index:Self.Index, element:Self.Iterator.Element)?</div><div class=""><br class=""></div></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* Is the problem being addressed significant enough to warrant a change to Swift?<br class=""></div></div></blockquote><br class=""><div style="direction: ltr;" class="">yes, I use filter for this but I believe find() and index() should be merged for it to be worth it. </div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* Does this proposal fit well with the feel and direction of Swift?<br class=""></div></div></blockquote>yes but I believe index() should be renamed to find()</div><div style="direction: ltr;" class=""><br class=""><blockquote type="cite" class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""></div></div></blockquote>python.<br class=""><blockquote type="cite" class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br class=""></div></div></blockquote>read the proposal and suggested an extension of scope. <br class=""></div><br class=""></div></div></div><br class=""></body></html>