<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 26, 2016 at 4:08 PM, Dave Abrahams 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 class=""><br>
on Mon Apr 25 2016, Erica Sadun <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
<br>
> On Apr 25, 2016, at 7:15 PM, Xiaodi Wu via swift-evolution<br>
> <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> Yup, we're going to try to touch base, the authors of the current draft that<br>
> is, sometime this week. More to come, hopefully.<br>
><br>
> On Mon, Apr 25, 2016 at 8:13 PM, Dave Abrahams via swift-evolution<br>
> <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> After some reflection, I don't really want to see a construct like #3 in<br>
> the standard library, and Chris has clarified for me that the standard<br>
> library doesn't need to solve the migration problems created by the<br>
> removal of C-style “for” loops. So, if I have inadvertently killed<br>
> progress on this proposal by bringing it up, please allow me to retract<br>
> item 3 above.<br>
><br>
> * Strides break down into: walks along the integer number line and walks along<br>
> the floating<br>
> point number line. We need to fix the math<br>
<br>
</span>There are walks along countable sets (for example, the set of Ints<br>
bounded by two UnsafePointer<Int>s) and walks along uncountable sets<br>
(for example, the rational numbers between 0 and 1).<br>
<span class=""><br>
> * For in need to work for collections, integer ranges, and strides for basic<br>
> iteration.<br>
><br>
> * Advanced `for` work is already addressed with mapping and Kevin Ballard's<br>
> proposed iterate and takeWhile<br>
><br>
> * Everyone but me has been traveling so getting things together has been a<br>
> little hard.<br>
><br>
> * I have been on Nate's case a lot about what collections, strides, sequences,<br>
> etc mean and should be named.<br>
<br>
</span>Thanks for the update. FWIW I don't expect anything of anyone; I just<br>
wanted to let everybody involved know that it could still get fixed for<br>
Swift 3 but we'll need to move fast.</blockquote><div><br></div><div>Appreciate the heads-up--faster movement forthcoming :)</div><div><br></div><div><br></div></div></div></div>