cadey
/
nim-wiki
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated Unofficial FAQ (markdown)

This commit is contained in:
Sinatra 2015-06-05 14:42:35 -04:00
parent ae313cef93
commit 201a0e15d8
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Unofficial-FAQ.md
View File

@ -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! 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: 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: