| ... | ... | @@ -21,19 +21,19 @@ clarity. |
| 21 | 21 | * Compatible with C libraries with no wrapper necessary. Directly include |
| 22 | 22 | C .h files and get access to the functions and symbols therein. |
| 23 | 23 | * Provides standard library which competes with the C standard library and is |
| 24 | | always compiled against statically in source form. Compile units do not |
| 24 | always compiled against statically in source form. Zig binaries do not |
| 25 | 25 | depend on libc unless explicitly linked. |
| 26 | | * Nullable type instead of null pointers. |
| 26 | * Optional type instead of null pointers. |
| 27 | 27 | * Safe unions, tagged unions, and C ABI compatible unions. |
| 28 | 28 | * Generics so that one can write efficient data structures that work for any |
| 29 | 29 | data type. |
| 30 | 30 | * No header files required. Top level declarations are entirely |
| 31 | 31 | order-independent. |
| 32 | 32 | * Compile-time code execution. Compile-time reflection. |
| 33 | | * Partial compile-time function evaluation with eliminates the need for |
| 33 | * Partial compile-time function evaluation which eliminates the need for |
| 34 | 34 | a preprocessor or macros. |
| 35 | 35 | * The binaries produced by Zig have complete debugging information so you can, |
| 36 | | for example, use GDB or MSVC to debug your software. |
| 36 | for example, use GDB, MSVC, or LLDB to debug your software. |
| 37 | 37 | * Built-in unit tests with `zig test`. |
| 38 | 38 | * Friendly toward package maintainers. Reproducible build, bootstrapping |
| 39 | 39 | process carefully documented. Issues filed by package maintainers are |