doc(readme): make limitations way more prominent

Byron · Byron · commit a36fbeb41ce0 · 2016-12-08T11:59:00.000+01:00
Also inform about the likelyhood of leaking system resources.

[skip ci]
diff --git a/README.md b/README.md
@@ -5,6 +5,12 @@ When reading from many possibly large files in a fashion similar to random acces
 Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications.
 
 
+## Limitations
+
+* **System resources (file-handles) are likely to be leaked!** This is due to the library authors reliance on a deterministic `__del__()` destructor.
+* The memory access is read-only by design.
+* In python below 2.6, memory maps will be created in compatibility mode which works, but creates inefficient memory mappings as they always start at offset 0.
+
 
 ## Overview
 
@@ -33,11 +39,6 @@ For performance critical 64 bit applications, a simplified version of memory map
 
 The package was tested on all of the previously mentioned configurations.
 
-## Limitations
-
-* The memory access is read-only by design.
-* In python below 2.6, memory maps will be created in compatibility mode which works, but creates inefficient memory mappings as they always start at offset 0.
-
 ## Installing smmap
 
 [![Documentation Status](https://readthedocs.org/projects/smmap/badge/?version=latest)](https://readthedocs.org/projects/smmap/?badge=latest)
