• words_number@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    8 days ago

    Isn’t it obvious? More code to skim, scroll over and maintain if something changes. If you add a struct field, your manual EQ implementation still compiles and seems to work but is wrong and will lead to bugs. Yes, solving this for 99,999% of cases with an attribute is just far superior and does make a difference (while keeping it easy to manually implement it if needed). Hash and Ord and some other traits can be implemented in a similar fashion btw…

    • PeriodicallyPedantic@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      8 days ago

      I said it was better, just not much better.

      The maintenance costs of equals is nearly zero. Scrolling over boilerplate seems like a real stretch, like saying a novel with a picture every chapter is harder to read.

      I like that you can’t accidentally forget to update it, which is kinda nice but is rarely a concern.
      And it’s a bit more readable, which is nice.
      It’s better, but folks are talking like it’s Super Jesus and I think it’s more like finding a dollar in the parking lot.

      • words_number@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        6 days ago

        Who said it was superjesus? It’s one of the smaller points on the long list of rusts advantages over other systems level PLs, but nonetheless notable. Especially if you consider that the feature that makes this possible is used for a ton of other useful stuff. And seriously, the boilerplate does matter, especially if you also add Ord, Hash and Debug impls. Your comparison with pictures in a noval makes no sense, since these add something valuable to the text and are easily distinguished from it. Heaps of boilerplate at a glance look just as meaningful as important sections of code, so being able to avoid it makes navigation significantly easier.