# Integers

Move supports six unsigned integer types: `u8`

, `u16`

, `u32`

, `u64`

, `u128`

, and `u256`

. Values of these types range from 0 to a maximum that depends on the size of the type.

## Literals

Literal values for these types are specified either as a sequence of digits (e.g.,`112`

) or as hex literals, e.g., `0xFF`

. The type of the literal can optionally be added as a suffix, e.g., `112u8`

. If the type is not specified, the compiler will try to infer the type from the context where the literal is used. If the type cannot be inferred, it is assumed to be `u64`

.

Number literals can be separated by underscores for grouping and readability. (e.g.,`1_234_5678`

, `1_000u128`

, `0xAB_CD_12_35`

).

If a literal is too large for its specified (or inferred) size range, an error is reported.

### Examples

## Operations

### Arithmetic

Each of these types supports the same set of checked arithmetic operations. For all of these operations, both arguments (the left and right side operands) *must* be of the same type. If you need to operate over values of different types, you will need to first perform a cast. Similarly, if you expect the result of the operation to be too large for the integer type, perform a cast to a larger size before performing the operation.

All arithmetic operations abort instead of behaving in a way that mathematical integers would not (e.g., overflow, underflow, divide-by-zero).

### Bitwise

The integer types support the following bitwise operations that treat each number as a series of individual bits, either 0 or 1, instead of as numerical integer values.

Bitwise operations do not abort.

### Bit Shifts

Similar to the bitwise operations, each integer type supports bit shifts. But unlike the other operations, the righthand side operand (how many bits to shift by) must *always* be a `u8`

and need not match the left side operand (the number you are shifting).

Bit shifts can abort if the number of bits to shift by is greater than or equal to `8`

, `16`

, `32`

, `64`

, `128`

or `256`

for `u8`

, `u16`

, `u32`

, `u64`

, `u128`

and `u256`

respectively.

### Comparisons

Integer types are the *only* types in Move that can use the comparison operators. Both arguments need to be of the same type. If you need to compare integers of different types, you will need to cast one of them first.

Comparison operations do not abort.

### Equality

Like all types with `drop`

in Move, all integer types support the "equal" and "not equal" operations. Both arguments need to be of the same type. If you need to compare integers of different types, you will need to cast one of them first.

Equality operations do not abort.

For more details see the section on equality

## Casting

Integer types of one size can be cast to integer types of another size. Integers are the only types in Move that support casting.

Casts *do not* truncate. Casting will abort if the result is too large for the specified type

Here, the type of `e`

must be `8`

, `16`

, `32`

, `64`

, `128`

or `256`

and `T`

must be `u8`

, `u16`

, `u32`

, `u64`

, `u128`

oe `u256`

.

For example:

`(x as u8)`

`(y as u16)`

`(873u16 as u32)`

`(2u8 as u64)`

`(1 + 3 as u128)`

`(4/2 + 12345 as u256)`

## Ownership

As with the other scalar values built-in to the language, integer values are implicitly copyable, meaning they can be copied without an explicit instruction such as `copy`

.