You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally, I think that if the performance cost is not too high I might even compare variables using the tuple notation. It is easier to understand and to read than the && syntax:
After the following discussion on https://github.com/dotnet/coreclr/issues/6520#issuecomment-236152874 we discovered ValueTuple did not implement the == and != operators.
I think this is an oversight, it looks pretty natural to me to write:
OR
Personally, I think that if the performance cost is not too high I might even compare variables using the tuple notation. It is easier to understand and to read than the
&&
syntax:instead of:
This might overlap with the Tuple Patterns but I think those were removed from C# 7. Having to call .Equals seems very ugly to me.
The text was updated successfully, but these errors were encountered: