feat: Add keyed equality concept #747
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dr1rrb
force-pushed
the
dev/dr/keyEq
branch
from
3608e87
to
f73e58c
Compare
dr1rrb
commented
Sep 22, 2022
carldebilly
approved these changes
Sep 22, 2022
dr1rrb
commented
Sep 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
related issue: #688
Feature
Add keyed equality concept
What is the current behavior?
We don't have any standardized solution to track immutable items.
What is the new behavior?
The
IKeyEquatable(andKeyEqualityComparer) can be used to easily track 2 versions of a same item.PR Checklist
Screenshots Compare Test Runresults.