mirror of
https://github.com/ziglang/zig.git
synced 2025-12-07 06:43:07 +00:00
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
18 lines
407 B
Zig
18 lines
407 B
Zig
const std = @import("../../index.zig");
|
|
const testing = std.testing;
|
|
const math = std.math;
|
|
const cmath = math.complex;
|
|
const Complex = cmath.Complex;
|
|
|
|
pub fn conj(z: var) Complex(@typeOf(z.re)) {
|
|
const T = @typeOf(z.re);
|
|
return Complex(T).new(z.re, -z.im);
|
|
}
|
|
|
|
test "complex.conj" {
|
|
const a = Complex(f32).new(5, 3);
|
|
const c = a.conjugate();
|
|
|
|
testing.expect(c.re == 5 and c.im == -3);
|
|
}
|