On: Go 2, here we come

[greenleafjacob]

> if this int or uint under or overflows, throw an exception

Overflow flags are supported on some architectures, so it would really just be a matter of checking that flag.

[4ad → greenleafjacob]

Except in Go, types are defined using modular 2s complement. Overflow is not considered a problem, it's a feature that code depends on.

[LukeShu → 4ad]

The spec says:

> For signed integers, the operations +, -, , /, and << may legally overflow and the resulting value exists and is deterministically defined by …*

It does not go on to define the overflow values; that gets to be implementation defined.

This is in contrast to unsigned integers, which the spec does precisely define overflow for.