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
Technically, @assert calls are not guaranteed to be run depending on the optimization level that Julia is run at, but in practice right now they always do. In the future this might not be the case. It is recommended that checks on function arguments / user data be done with error throws (e.g., if x < 0; throw(DomainError ...); end) or an alternative implementation like ArgCheck.jl that is always guaranteed to run.
I don't care to fix this right now but it is worth keeping an eye on in future releases.
The text was updated successfully, but these errors were encountered:
Technically,
@assert
calls are not guaranteed to be run depending on the optimization level that Julia is run at, but in practice right now they always do. In the future this might not be the case. It is recommended that checks on function arguments / user data be done with error throws (e.g.,if x < 0; throw(DomainError ...); end
) or an alternative implementation like ArgCheck.jl that is always guaranteed to run.I don't care to fix this right now but it is worth keeping an eye on in future releases.
The text was updated successfully, but these errors were encountered: