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
23 lines
581 B
Zig
23 lines
581 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 pow(comptime T: type, z: T, c: T) T {
|
|
const p = cmath.log(z);
|
|
const q = c.mul(p);
|
|
return cmath.exp(q);
|
|
}
|
|
|
|
const epsilon = 0.0001;
|
|
|
|
test "complex.cpow" {
|
|
const a = Complex(f32).new(5, 3);
|
|
const b = Complex(f32).new(2.3, -1.3);
|
|
const c = pow(Complex(f32), a, b);
|
|
|
|
testing.expect(math.approxEq(f32, c.re, 58.049110, epsilon));
|
|
testing.expect(math.approxEq(f32, c.im, -101.003433, epsilon));
|
|
}
|