From 201a0e15d83014fa5f494500c7f2edd4da796d91 Mon Sep 17 00:00:00 2001 From: Sinatra Date: Fri, 5 Jun 2015 14:42:35 -0400 Subject: [PATCH] Updated Unofficial FAQ (markdown) --- Unofficial-FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Unofficial-FAQ.md b/Unofficial-FAQ.md index 6244003..0234578 100644 --- a/Unofficial-FAQ.md +++ b/Unofficial-FAQ.md @@ -62,7 +62,7 @@ Then you are likely trying to compile the C sources with a 64bit version of GCC. If the error does not resemble the above then the problem is likely with the C sources. Ask for help on IRC or submit an issue on github! -## Is Nim unsafe? +# Is Nim unsafe? Usually this comes from Nim's ability to dereference null pointers and it's deal with compiling to C IR. Nim strives to generate C IR that won't cause undefined behavior as easy as how it can be caused by hand written C code. But when there is hand-written Nim code that contains errors like dereferencing a null pointer, there are ways to avoid this: