- cross-posted to:
- programming@kbin.social
- golang@lemmy.ml
- cross-posted to:
- programming@kbin.social
- golang@lemmy.ml
You must log in or register to comment.
So it’s not really a problem with for loops, it’s a problem with closures inside for loops.
As someone just learning Go, the current behaviour is really unexpected. I’m happy that they are changing it.
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.
Much needed change, I wish they made it apply for all go versions though
