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

typo on flag

This commit is contained in:
Ben Walding 2015-06-06 16:08:08 +10:00
parent 201a0e15d8
commit 21e9b809cd
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

@ -69,7 +69,7 @@ Usually this comes from Nim's ability to dereference null pointers and it's deal
- `not nil` Annotation: - `not nil` Annotation:
- You can use this annotation on any nilable type in your code and the compiler statically checks at compile time that your code can't possibly have a null pointer for that var - You can use this annotation on any nilable type in your code and the compiler statically checks at compile time that your code can't possibly have a null pointer for that var
- Compiler flags: - Compiler flags:
- you can pass flags like `-fsanitze`, or `-fsanitize=null` for nil checks, which provide minimal overhead. - you can pass flags like `-fsanitize`, or `-fsanitize=null` for nil checks, which provide minimal overhead.
- In the near future, `-nilChecks:On|Off` will be available for explicit nil checking and instead of Segmentation Faults, when a null pointer is dereferenced, it will be a NilError Exception - In the near future, `-nilChecks:On|Off` will be available for explicit nil checking and instead of Segmentation Faults, when a null pointer is dereferenced, it will be a NilError Exception
- Also in the near future, `-d:safety` will be available to use along with `-d:release` for performance _and_ safety (see: [#2809](https://github.com/Araq/Nim/issues/2809)) - Also in the near future, `-d:safety` will be available to use along with `-d:release` for performance _and_ safety (see: [#2809](https://github.com/Araq/Nim/issues/2809))
- `-d:release` config - `-d:release` config