Go 1.21 shipped a preview of a change in Go 1.22 to make for loops less error-prone.
  • mrkite
    7·
    1 year ago

    So it’s not really a problem with for loops, it’s a problem with closures inside for loops.

  • lightsecond
    5·
    1 year ago

    As someone just learning Go, the current behaviour is really unexpected. I’m happy that they are changing it.

    • bmarinov@lemmy.world
      7·
      1 year ago

      As someone with years of Go experience, this thing bites me or my team in the ass at least once every six months. Sometimes tests catch it, other times the tests get written after the fact and made to fit the implementation. Hilarious bug hunts ensue. I’m happy for this proposal moving forward.

  • austinMEnglish
    4·
    1 year ago

    Much needed change, I wish they made it apply for all go versions though