Even if the tool works perfectly, you have to run it every time you change something. It’s not the end of the world, but it’s still much nicer to just have a macro to derive it at compile time.
What if youre working with library types? The problem is not not you compare a bunch of fields but that the implementation on those members is most likely bad.
I’ve only had to implement equality in C# but that didn’t seem that hard of a problem. you just expand the operator = function
It’s not hard, just if you’re doing it for a struct with a lot of fields it’s a lot of boilerplate
I just use the HashCode class and compare the results.
Pretty sure there’s a source generator for it as well nowadays.
My IDE can do that for me. And it was able to do that pre AI boom. Yes, the code ends up more verbose, but I just collapse it.
So from a modern dev UX perspective, this shouldn’t be a major difference.
Even if the tool works perfectly, you have to run it every time you change something. It’s not the end of the world, but it’s still much nicer to just have a macro to derive it at compile time.
What if youre working with library types? The problem is not not you compare a bunch of fields but that the implementation on those members is most likely bad.
Then you should also override
Equals(object),GetHashCode, and implementIEquatable<T>.Thankfully a lot of the usual boilerplate code can be avoided using a
recordclass or struct: