@@ -21,7 +21,7 @@ function test_approx(
21
21
msg= " " ;
22
22
kwargs... ,
23
23
)
24
- @test_msg msg isapprox (actual, expected; kwargs... )
24
+ @test_msg msg isapprox (actual, expected; nans = true , kwargs... )
25
25
end
26
26
27
27
for (T1, T2) in ((AbstractThunk, Any), (AbstractThunk, AbstractThunk), (Any, AbstractThunk))
@@ -62,7 +62,7 @@ The `kwargs` are passed on to `isapprox`
62
62
function _can_pass_early (actual, expected; kwargs... )
63
63
actual == expected && return true
64
64
try
65
- return isapprox (actual, expected; kwargs... )
65
+ return isapprox (actual, expected; nans = true , kwargs... )
66
66
catch err
67
67
# Might MethodError, might DimensionMismatch, might fail for some other reason
68
68
# we don't care, whatever errored it means we can't quit early
@@ -158,7 +158,7 @@ It matters primarily for types that overload `add!!` such as `InplaceableThunk`s
158
158
`acc` is the value that has been accumulated so far.
159
159
`val` is a deriviative, being accumulated into `acc`.
160
160
161
- `kwargs` are all passed on to isapprox
161
+ `kwargs` are all passed on to ` isapprox`
162
162
"""
163
163
function _test_add!!_behaviour (acc, val; kwargs... )
164
164
# Note, we don't test that `acc` is actually mutated because it doesn't have to be
0 commit comments