• @DarthFrodo@lemmy.world
    link
    fedilink
    2311 months ago

    The neat thing is, you can add stuff like range checks and logging for getters and setters without changing every call. Separation of concerns is also vital in larger projects.

    • @jazz
      link
      611 months ago

      also const correctness in languages that support that concept

    • @PeWu@lemmy.ml
      link
      fedilink
      111 months ago

      Yeah, I need to force myself to do it, cuz it feels so slick and efficient and overall nice. Or am I just dumb and didn’t understand satire of this post.

    • @PeWu@lemmy.ml
      link
      fedilink
      111 months ago

      Yeah, I need to force myself to do it, cuz it feels so slick and efficient and overall nice. Or am I just dumb and didn’t understand satire of this post.

  • @alokir@lemmy.world
    link
    fedilink
    411 months ago

    Wait until you hear about the concept of properties in languages like Javascript, C#, Kotlin and many others.

    • @relevants@feddit.de
      link
      fedilink
      311 months ago

      At least for Kotlin it’s literally just syntactic sugar for getter and setter methods. I really like them, don’t get me wrong, but it’s just the bottom approach masquerading as the top approach

  • metarmask
    link
    fedilink
    311 months ago

    That’s not a new way to change data, it’s reading it.

  • @watermelonsushi@lemmy.fmhy.ml
    link
    fedilink
    111 months ago

    I love dart’s approach to getter and setter methods… They let you define methods labelled explicitly as “get” or “set” methods that you can call without writing the parentheses. So the call looks like accessing a member variable, but internally it can handle additional functionality like logging or validation or whatever you want. So the syntax would look like the first example in the meme, but with all the benefits of the second example. I wish more languages would incorporate this