[swift-evolution] Feature proposal: Range operator with step
Erica Sadun
erica at ericasadun.com
Wed Apr 6 13:26:02 CDT 2016
> On Apr 6, 2016, at 12:23 PM, Stephen Canon via swift-evolution <swift-evolution at swift.org> wrote:
>
>
>> On Apr 6, 2016, at 11:20 AM, Stephen Canon via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>
>>> On Apr 6, 2016, at 11:16 AM, Dave Abrahams via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>>
>>> One question that I *do* think we should answer, is whether the elements
>>> of
>>>
>>> (0..<199).striding(by: -2)
>>>
>>> are even or odd.
>>
>> Odd. I don’t believe that many real use cases care, but odd is more efficient from a performance perspective. Needs to be documented clearly, however.
>
> Sorry, I was thinking of (0…199).striding(by: -2).
>
> For the (0..<199) case, Erica’s assessment seems about right, though it isn’t at all obvious how it generalizes to floating point strides.
(l..<h).striding(by: -dX) is undefined for floating point strides as there cannot be a starting value.
-- E
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160406/ccc7ca6a/attachment.html>
More information about the swift-evolution
mailing list