authorgravatar for n@nirf.deNick Erdmann <n@nirf.de> 2019-07-16 01:48:47+02:00
committergravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2019-07-15 19:52:07-04:00
log33eaaadd01b20d1327b67758664ce1265216e471
tree93f594dabb65ca2c2f66180589087bff2c5ac0af
parent7d9ee5d6d53011e9edc7ca10b76d64af807a833f

fix documentation of assert

1 files changed, 1 insertions(+), 1 deletions(-)

std/debug.zig+1-1
...@@ -199,7 +199,7 @@ pub fn dumpStackTrace(stack_trace: builtin.StackTrace) void {...@@ -199,7 +199,7 @@ pub fn dumpStackTrace(stack_trace: builtin.StackTrace) void {
199/// in its heuristics.199/// in its heuristics.
200/// Inside a test block, it is best to use the `std.testing` module rather200/// Inside a test block, it is best to use the `std.testing` module rather
201/// than this function, because this function may not detect a test failure201/// than this function, because this function may not detect a test failure
202/// in ReleaseFast and ReleaseSafe mode. Outside of a test block, this assert202/// in ReleaseFast and ReleaseSmall mode. Outside of a test block, this assert
203/// function is the correct function to use.203/// function is the correct function to use.
204pub fn assert(ok: bool) void {204pub fn assert(ok: bool) void {
205 if (!ok) unreachable; // assertion failure205 if (!ok) unreachable; // assertion failure