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
InEpsilonSlice is implemented as a series of calls to InEpsilon (which is not unexpected), but when it calls InEpsilon, it does not pass the msgAndArgs ...interface{}. As a result, the failures are not very helpful, because the default output of InEpsilon only tells the relative error, not the expected & actual values.
It isn't immediately obvious to me how InEpsilonSlice should deal with the messages when calling InEpsilon-- especially if there are multiple mismatches, would you want to print the same message each time?
The text was updated successfully, but these errors were encountered:
InEpsilonSlice
is implemented as a series of calls toInEpsilon
(which is not unexpected), but when it callsInEpsilon
, it does not pass themsgAndArgs ...interface{}
. As a result, the failures are not very helpful, because the default output ofInEpsilon
only tells the relative error, not the expected & actual values.It isn't immediately obvious to me how
InEpsilonSlice
should deal with the messages when callingInEpsilon
-- especially if there are multiple mismatches, would you want to print the same message each time?The text was updated successfully, but these errors were encountered: