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
22 lines
537 B
Zig
22 lines
537 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 cos(z: var) Complex(@typeOf(z.re)) {
|
|
const T = @typeOf(z.re);
|
|
const p = Complex(T).new(-z.im, z.re);
|
|
return cmath.cosh(p);
|
|
}
|
|
|
|
const epsilon = 0.0001;
|
|
|
|
test "complex.ccos" {
|
|
const a = Complex(f32).new(5, 3);
|
|
const c = cos(a);
|
|
|
|
testing.expect(math.approxEq(f32, c.re, 2.855815, epsilon));
|
|
testing.expect(math.approxEq(f32, c.im, 9.606383, epsilon));
|
|
}
|