impl EqualValues 2 objects have (T) Equal(T) bool
#1093
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
when using
EqualValues
for 2 objects which are of the same type and implement an(T) Equal(T) bool
method, use the method to compare.Tbh I'd almost put this in
Equal
, butEqualValues
is more correct...I chose not to implement supporting
EqualValues(Foo{1}, &Foo{1})
, though I do have a branch with it implemented ...Motivation
This seems very much inline with many many other languages and makes it much easier to compare custom types, ranging from application level types to
decimal.Decimal
.