Rusty 🦀 Femboy 🏳️🌈@lemmy.blahaj.zone to Programmer HumorEnglish · 10 hours agoI love Rustlemmy.blahaj.zoneimagemessage-square42fedilinkarrow-up1169arrow-down112
arrow-up1157arrow-down1imageI love Rustlemmy.blahaj.zoneRusty 🦀 Femboy 🏳️🌈@lemmy.blahaj.zone to Programmer HumorEnglish · 10 hours agomessage-square42fedilink
minus-squareGonzako@lemmy.worldlinkfedilinkarrow-up4arrow-down1·9 hours agoI’ve only had to implement equality in C# but that didn’t seem that hard of a problem. you just expand the operator = function
minus-squareporous_grey_matterlinkfedilinkarrow-up8·8 hours agoIt’s not hard, just if you’re doing it for a struct with a lot of fields it’s a lot of boilerplate
minus-squareGetOffMyLan@programming.devlinkfedilinkarrow-up5arrow-down1·edit-27 hours agoI just use the HashCode class and compare the results. Pretty sure there’s a source generator for it as well nowadays.
minus-squareDeckweiss@lemmy.worldlinkfedilinkarrow-up1arrow-down5·edit-27 hours agoMy 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.
minus-squareporous_grey_matterlinkfedilinkarrow-up4arrow-down1·7 hours agoEven 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.
minus-squarecopygirl@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up4·7 hours agoThen you should also override Equals(object), GetHashCode, and implement IEquatable<T>. Thankfully a lot of the usual boilerplate code can be avoided using a record class or struct: public record Person(string Name, uint Age);
minus-squareGonzako@lemmy.worldlinkfedilinkarrow-up1·3 hours agoOh well, It does show how little I do have to actually use that. It just hasn’t come up that much
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.
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:Oh well, It does show how little I do have to actually use that. It just hasn’t come up that much