4 ms·
If you never did a mistake connected to this and caused a bug in real prod code, you haven’t been writing go for long enough.
by shp0ngle 4y ago
If you never did a mistake connected to this and caused a bug in real prod code, you haven’t been writing go for long enough.
- barsonme 4y agoEhhhh, I’ve been writing Go for ~10 years and I’ve never had this make it into prod. Many times in local development and testing, though.
- Traubenfuchs 4y agoIdeally at least one of the tests out of your testing pyramid would catch something like that though.
- Cthulhu_ 4y agoIdeally yeah, but unfortunately very few people work in ideal circumstances.
- bandrami 4y agoI internalized early on that the likelihood of this mistake means Go wants me to refactor when I find myself liable to making it.
- ainar-g 4y agoOr you've been using the looppointer analyser[1] from the start, heh. [1]: https://github.com/kyoh86/looppointer https://github.com/kyoh86/looppointer
- viiralvx 4y agoYeahhhhh, I worked at a big company on their CI product and I had this bug bite me and break builds for a little bit. Luckily caught my mistake and fixed it within 15 minutes, but it's always easy to overlook.