sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate

sizes. Besides the int data type, Nim has some more data types for signed and unsigned integers: int8, int16, int32, and int64 are signed types with well-defined bit and byte size, and uint8, uint16 may have to do type conversion in that case before the math operation can be applied. Adding two int8 types on some CPUs can be slower than adding two ints, because the CPU may have to size extend the backend, is that unsigned integers do not generate overflow errors but simply wrap around: var x: int8 = 0 while true: inc(x) echo x The code above would print the numbers 0 through 127, then terminate