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
If one defines isequal one has to define hash as well since otherwise the two are not consistent. In general, if one does not care about floating point comparisons one should just define == instead of isequal since isequal falls back to ==. Here it probably would make sense to define both since it would lead to different comparisons of the kernel parameters and parameters of the transform.
If one defines
isequal
one has to definehash
as well since otherwise the two are not consistent. In general, if one does not care about floating point comparisons one should just define==
instead ofisequal
sinceisequal
falls back to==
. Here it probably would make sense to define both since it would lead to different comparisons of the kernel parameters and parameters of the transform.Basically, most often one wants the recursive implementation in JuliaServices/AutoHashEquals.jl#18.
Originally posted by @devmotion in #335 (comment)
The text was updated successfully, but these errors were encountered: