You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a heavy user of @inferred I'd like it to be a little more user friendly and consistent with the other testing macros. My main gripe is that it's a test in its own right; I'd like to be able to write @test_inferred f(x) and have it register with the current test set, rather than unilaterally throwing an exception on failure.
The @test_warn macro does exactly this, and also returns the result so that it can be composed with @test if desired:
As a heavy user of
@inferred
I'd like it to be a little more user friendly and consistent with the other testing macros. My main gripe is that it's a test in its own right; I'd like to be able to write@test_inferred f(x)
and have it register with the current test set, rather than unilaterally throwing an exception on failure.The
@test_warn
macro does exactly this, and also returns the result so that it can be composed with@test
if desired:See related discussion over at: #20348 (comment)
I think there's two separate decisions here:
@inferred
register the result with the current test set@test_inferred
for consistency with other testing macros.The text was updated successfully, but these errors were encountered: