I think my opinion is largely the same. A range is not a stride, and sometimes we have use for striding backwards, a use case that shouldn't be penalized. +1 to the free function.<br><br>I wouldn't mind, orthogonally, a way to express (a, b] as a range. It just seems like that should be of use, somewhere.<br><br>Finally, orthogonal to all of the above, I'm super eager to end error accumulation in floating point strides.<br><div class="gmail_quote"><div dir="ltr">On Tue, Apr 5, 2016 at 6:52 PM Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Apr 5, 2016, at 5:22 PM, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><div><span style="font-family:Palatino-Roman;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I don't think that's obvious at all, because 0 ≮ 10</span><br style="font-family:Palatino-Roman;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></div></blockquote></div><br></div><div style="word-wrap:break-word"><div>Points brought up elsewhere:</div><div><br></div><div>* A range does not have direction, it is is an area of variation between lower and upper limits.</div><div>* A range does not go from a larger amount to a smaller amount because it is not a sequence</div><div>* Much of this problem goes away with striding (as Dave pointed out several times, sorry Dave)</div><div><br></div><div>After consideration, I have been persuaded to the opinion that</div></div><div style="word-wrap:break-word"><div><br></div><div><blockquote type="cite" style="font-family:Palatino-Roman"> stride(from: 0, to: -10, by: -1)</blockquote><br></div></div><div style="word-wrap:break-word"><div>and </div><div><br></div><div><blockquote type="cite" style="font-family:Palatino-Roman"> (-9...0).reverse()</blockquote><br></div><div>both represent the numbers -9, -8,...,0 better than any alternatives I have offered. I still</div><div>prefer the stride version for intent and clarity.</div><div><br></div><div>That said, I also prefer my revised SE-0051 semantics for better representing what strides will</div><div>attempt to do.</div></div><div style="word-wrap:break-word"><div><br></div><div>-- Erica</div></div><div style="word-wrap:break-word"><div>p.s. Thanks all for the patient explanations</div><div><br></div><div><br></div><div><br></div><div><br></div></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">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>