Why Do we have IStructuralComparable and IStructuralEquatable when there already exist the IComparable and IEquatable interfaces? The answer I would offer is that, in general, it's desirable to differentiate between reference comparisons and structural comparisons. = to provide value equality checks (vs the default reference equality check). The MSDN documentation https://c-object-kullan-m63949.wikicorrespondence.com/3674389/en_son_beş_c_istructuralequatable_kullanımı_kentsel_haber