Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BeEquivalentTo on normal tuples should use structural equivalency #1206

Merged
merged 1 commit into from Dec 18, 2019

Conversation

@dennisdoomen
Copy link
Member

dennisdoomen commented Dec 18, 2019

Unlinke ValueTuple<>, the older Tuple<> was treated as a value type instead of something that requires a structural equality check.

Fixed #999

Unlinke ValueTuple<>, the older Tuple<> was treated as a value type instead of something that requires a structural equality check.
@dennisdoomen dennisdoomen requested a review from jnyrup Dec 18, 2019
@jnyrup
jnyrup approved these changes Dec 18, 2019
@dennisdoomen dennisdoomen merged commit f60927f into fluentassertions:master Dec 18, 2019
1 check passed
1 check passed
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
@dennisdoomen dennisdoomen deleted the dennisdoomen:Fix/Tuples branch Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.