It's normally expected that if you implement IEquatable.Equals you will also override Object.Equals to be consistent. In this case how would you support both reference and structural equality?

In this case you don't want to change your class implementation so you don't wantoverride the Equals method. this will define a general way to compare objects in your application.

It differs from reference equality, which indicates that two object references are equal because they reference the same physical object.

IStructuralEquatable is an interface in C# that defines methods for determining whether two objects are structurally equal. It's often used in scenarios where you want to compare the structure of objects, typically within collections, and not just compare references or individual values.

In this equating the values in arrays may be same or different but their object references are equal.

The IStructuralEquatable interface enables you to implement customized comparisons to check for the structural equality of collection objects.

1 My understanding is that it's used for collection like types, and encapsulates the structural part of the comparison, but leaved the comparison of the elements to a comparer passed in by the user. But I'm not really sure if I really got it.

When an implementer overrides the virtual Equals method in a struct, the purpose is to provide a more efficient means of performing the value equality check and optionally to base the comparison on some subset of the struct's field or properties.

(doesn't violate documentation), but it is clearly hamiş kakım good as it would be if 0 were replaced with C# IStructuralEquatable Kullanımı i. Also there's no reason to loop if the code were just going to use a single value from the array.

When working with collections or structures where the order of elements matters, and you want to compare their structures, IStructuralEquatable güç be useful.

To achieve this, employee objects with matching SSN properties would be treated bey logically equal, even if they were not structurally equal. Share Improve this answer Follow

Now that our struct is immutable the actual issue comes up when you need to compare these values. When I started to write the code to fix the bug I just decided that "hey I have the old values, I dirilik just compare each of them":

Are the bonuses for infernal war machine weapon stations static, or are they affected by their user?

Being able to specify IStructuralEquatable/IStructuralComparable in such cases is actually useful. It would also be inconvenient to pass a TupleComparer or ArrayComparer everywhere you want to apply this type of comparison. The two approaches are not mutually exclusive.