<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 1, 2016, at 10:36 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 1, 2016, at 1:54 AM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">It's so nice to see such care devoted to clarifying these existing<br class="">names. I agree with the premise that stride(to:by:) and<br class="">stride(through:by:) are poorly named, but I'd like to make two<br class="">critiques of this proposal--<br class=""></div></div></blockquote></div></div></div></blockquote></div><br class=""><div class="">Updated proposal: <a href="https://gist.github.com/erica/2745585a4aac442db1fc" class="">https://gist.github.com/erica/2745585a4aac442db1fc</a></div></body></html>