> On Dec 4, 2017, at 10:53, Karl Wagner wrote:
>
> But you noted in that thread that "(Int.min.. you can fit in an Int, and causes a crash today. If we remove IndexDistance,
> that behaviour is locked-in, is it not?
>
That behavior is going to be locked in whether we like it or not when we
d
But you noted in that thread that "(Int.min.. On 4. Dec 2017, at 19:39, Ben Cohen via swift-evolution
> wrote:
>
> They will continue to conform to Collection just as they do today.
> Range.IndexDistance is already an Int.
>
>> On Dec 4, 2017, at 10:35, Karl Wagner via swift-evolution
>> mail
They will continue to conform to Collection just as they do today.
Range.IndexDistance is already an Int.
> On Dec 4, 2017, at 10:35, Karl Wagner via swift-evolution
> wrote:
>
> What does this mean for ranges of integers, as Xiaodi mentioned in the review
> thread? Can they still conform to
What does this mean for ranges of integers, as Xiaodi mentioned in the review
thread? Can they still conform to Collection?
I think we really need clarification on that aspect. Personally, I would
consider it a deal-breaker.
- Karl
> On 4. Dec 2017, at 18:57, Douglas Gregor via swift-evolutio
