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 you use a combinatoric matcher (e.g. all) and one of the sub-matchers returns a match_result that causes the matcher to fail, the "actual" value reported is whatever that match_result declared. This is generally wrong, since that value is probably only relevant to one of the sub-matchers, and doesn't show the entire value. For example:
The easy way to fix this would be for combinatoric matchers to return bools all the time, so that the full object is printed. However, there might be a better way that lets us see all the match_results. Maybe we should stop short-circuiting the combinatoric matchers too?
The text was updated successfully, but these errors were encountered:
If you use a combinatoric matcher (e.g.
all
) and one of the sub-matchers returns amatch_result
that causes the matcher to fail, the "actual" value reported is whatever thatmatch_result
declared. This is generally wrong, since that value is probably only relevant to one of the sub-matchers, and doesn't show the entire value. For example:This might print:
The easy way to fix this would be for combinatoric matchers to return
bool
s all the time, so that the full object is printed. However, there might be a better way that lets us see all thematch_result
s. Maybe we should stop short-circuiting the combinatoric matchers too?The text was updated successfully, but these errors were encountered: