> 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
But you noted in that thread that "(Int.min..
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
>
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
Proposal Link:
https://github.com/apple/swift-evolution/blob/master/proposals/0191-eliminate-indexdistance.md
Hello Swift Community,
The review of SE-0191 "Eliminate IndexDistance from Collection” ran from
November 27…December 3, 2017. The proposal is accepted. Feedback for this