• jcg@halubilo.social
    link
    fedilink
    arrow-up
    3
    ·
    7 hours ago

    Huh, I had never considered this solution to fizzbuzz to be honest. I usually go for string concatenation, or (i % 3 == 0 && i % 5 == 0), but yeah i % 15 == 0 is certainly a clever simplification

    • Bogasse@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      6 hours ago

      I think it’s worse at conveying the intention and should be a compile-time simplification (I’m too lazy to check if compilers would do it though).

  • ryannathans@aussie.zone
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    19 hours ago

    Isn’t the logic inverted? I think you want a == 0 on each of those conditions

    You wouldn’t even need the first if you removed the space

    • neukenindekeuken@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      6 hours ago

      Correct, noticed the same thing. Should have been a bang in front of each of the terms, your modulus of any of those will return a 0 when hit, which will convert to false and fail each of those conditions.

      This solution will do the opposite of what was intended unless the if conditions are inverted. Then it works flawlessly and the %15 is indeed a clever solution.

  • MachineFab812@discuss.tchncs.de
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    21 hours ago

    Ya’know, it shouldn’t be too hard to setup the ╔ and ╚ characters to function as or be substituted for quotes or brackets, depending on the language, then handle the rest as ligatures. Straight display substitution could allow for clean code and portable touch-typing, while still providing this sort of “visual training wheels” for those who want it in their own editor/ide