4 ms·
Definitely a good change, as this fixes an issue I (and I think most Go developers) have been bitten by more than once. It was really interesting to read the re
by benhoyt 3y ago
Definitely a good change, as this fixes an issue I (and I think most Go developers) have been bitten by more than once. It was really interesting to read the response of someone from the C# team in the original discussion, of how C# had gone through almost exactly the same change and how that went down: https://github.com/golang/go/discussions/56010#discussioncomment-3788526 https://github.com/golang/go/discussions/56010#discussioncom...
- jrochkind1 3y agoIt is so useful to compare analogous experiences from other languages, and I find not done often enough. For instance, i feel like ruby and python could probably learn a lot from each other, but it can seem like there just aren't enough people (myself also not) who are sufficiently expert at both to identify the lessons.
- tapirl 3y agoNot exactly. C# had never gone through the change on c-like for-loops.
- kreetx 3y agoYup, not a Go developer but ran into exactly this years ago when wanted to get a feel of it. Took a while to figure out what was wrong!