[swift-evolution] Improvement proposal: change overflow behavior in successor()/predecessor() methods for Int types

Dmitri Gribenko gribozavr at gmail.com
Thu Apr 7 12:54:29 CDT 2016

On Thu, Apr 7, 2016 at 12:20 AM, Vladimir.S via swift-evolution
<swift-evolution at swift.org> wrote:
> But. .successor() .predecessor() methods for Int values do not follow these
> rules for overflow situations. I.e. :
> let i : Int8 = Int8.max
> let k : Int8 = i.successor()
> - is OK for current Swift compiler. We have i==127 and k==-128, no run-time
> error.

This was done for performance reasons.  Array's indices are Ints, and
adding an overflow check here was causing significant performance
issues when iterating over arrays.  These methods were not designed to
be used in contexts other than indices.  When ints are used as
indices, doing an overflow check in successor() does not prevent any
mistakes, since Array's bounds are always tighter than

These methods are going away in the new indexing model.


(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

More information about the swift-evolution mailing list