From 848c58e3206859963fd546285e58db24d2d117cd Mon Sep 17 00:00:00 2001 From: ReneSac Date: Fri, 3 Apr 2015 20:43:17 -0300 Subject: [PATCH] removed unsigned part, as it is not a specific issue for python programmers --- Nim-for-Python-Programmers.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/Nim-for-Python-Programmers.md b/Nim-for-Python-Programmers.md index b003e68..8ce9316 100644 --- a/Nim-for-Python-Programmers.md +++ b/Nim-for-Python-Programmers.md @@ -97,12 +97,6 @@ Nim arrays can also be indexed from any number. That is, ``z: array[1..4, int]`` In Nim you are strongly discouraged from using pointers in Nim, and you can accomplish almost everything you'd otherwise use pointers for with normal arguments, "var" arguments, variables, and "ref". -### Unsigned integers - -Nim strongly discourages the use of unsigned integers, as it's considered unnecessary and somewhat unsafe* for most applications. The unsigned types uint, uint8/16/32/64 are available by default, but the arithmetic and binary functions are not defined. If you do need to do arithmetic on unsigned integers, you need to import the **unsigned** module. - -*See: http://critical.eschertech.com/2010/04/07/danger-unsigned-types-used-here/ - ### Object-Orientation