| ... | ... | @@ -25,6 +25,7 @@ Here are some examples: |
| 25 | 25 | |
| 26 | 26 | * [Iterative Replacement of C with Zig](http://tiehuis.github.io/blog/zig1.html) |
| 27 | 27 | * [The Right Tool for the Right Job: Redis Modules & Zig](https://www.youtube.com/watch?v=eCHM8-_poZY) |
| 28 | * [Writing a small ray tracer in Rust and Zig](https://nelari.us/post/raytracer_with_rust_and_zig/) |
| 28 | 29 | |
| 29 | 30 | Zig is a brand new language, with no advertising budget. Word of mouth is the |
| 30 | 31 | only way people find out about the project, and the more people hear about it, |
| ... | ... | @@ -45,8 +46,8 @@ The most highly regarded argument in such a discussion is a real world use case. |
| 45 | 46 | |
| 46 | 47 | The issue label |
| 47 | 48 | [Contributor Friendly](https://github.com/ziglang/zig/issues?q=is%3Aissue+is%3Aopen+label%3A%22contributor+friendly%22) |
| 48 | | exists to help contributors find issues that are "limited in scope and/or |
| 49 | | knowledge of Zig internals." |
| 49 | exists to help you find issues that are **limited in scope and/or |
| 50 | knowledge of Zig internals.** |
| 50 | 51 | |
| 51 | 52 | ### Editing Source Code |
| 52 | 53 | |
| ... | ... | @@ -61,8 +62,7 @@ To test changes, do the following from the build directory: |
| 61 | 62 | |
| 62 | 63 | 1. Run `make install` (on POSIX) or |
| 63 | 64 | `msbuild -p:Configuration=Release INSTALL.vcxproj` (on Windows). |
| 64 | | 2. `bin/zig build --build-file ../build.zig test` (on POSIX) or |
| 65 | | `bin\zig.exe build --build-file ..\build.zig test` (on Windows). |
| 65 | 2. `bin/zig build test` (on POSIX) or `bin\zig.exe build test` (on Windows). |
| 66 | 66 | |
| 67 | 67 | That runs the whole test suite, which does a lot of extra testing that you |
| 68 | 68 | likely won't always need, and can take upwards of 2 hours. This is what the |
| ... | ... | @@ -79,8 +79,8 @@ Another example is choosing a different set of things to test. For example, |
| 79 | 79 | not the other ones. Combining this suggestion with the previous one, you could |
| 80 | 80 | do this: |
| 81 | 81 | |
| 82 | | `bin/zig build --build-file ../build.zig test-std -Dskip-release` (on POSIX) or |
| 83 | | `bin\zig.exe build --build-file ..\build.zig test-std -Dskip-release` (on Windows). |
| 82 | `bin/zig build test-std -Dskip-release` (on POSIX) or |
| 83 | `bin\zig.exe build test-std -Dskip-release` (on Windows). |
| 84 | 84 | |
| 85 | 85 | This will run only the standard library tests, in debug mode only, for all |
| 86 | 86 | targets (it will cross-compile the tests for non-native targets but not run |
Andrew Kelley <andrew@ziglang.org> 2019-08-04 15:15:11-04:00
Commit is signed but in an unrecognized format.