c2db077574
Previously, std.debug.assert would `@panic` in test builds, if the assertion failed. Now, it's always `unreachable`. This makes release mode test builds more accurately test the actual code that will be run. However this requires tests to call `std.testing.expect` rather than `std.debug.assert` to make sure output is correct. Here is the explanation of when to use either one, copied from the assert doc comments: Inside a test block, it is best to use the `std.testing` module rather than assert, because assert may not detect a test failure in ReleaseFast and ReleaseSafe mode. Outside of a test block, assert is the correct function to use. closes #1304 |
||
|---|---|---|
| .. | ||
| compiler_rt | ||
| init-exe | ||
| init-lib | ||
| bootstrap_lib.zig | ||
| bootstrap.zig | ||
| build_runner.zig | ||
| builtin.zig | ||
| panic.zig | ||
| test_runner.zig | ||