100-go-mistakes
100-go-mistakes copied to clipboard
📖 100 Go Mistakes and How to Avoid Them
**Not considering Fuzz test** Since go 1.18, this kind of tests may help us to find out missing edge case. **Solution** Use it ;) .
Gophers in China are also interested in [100-go-mistakes-how-to-avoid-them](https://livebook.manning.com/book/100-go-mistakes-and-how-to-avoid-them/),but Chinese edition is not available yet. I wish to get your authorization to translate it into Chinese and publish it on Github...
Translation of the main content in Portugese. Reference: https://github.com/teivah/100-go-mistakes/blob/master/docs/index.md Example: Japanese translation https://github.com/teivah/100-go-mistakes/blob/master/docs/ja.md Advice: Step-wise approach (TL;DR blocks first, then the main content)
Knowing there will be a Japanese translation (released in August 2023), I would very much like this repo to offer a Japanese version of the README. If you're interested, feel...
As you may have noticed, I've been enriching the repo with much more content these past weeks. See https://100go.co. I only had a TL;DR in the past, and now I...
Thank you for such an incredible book. While reading the fourth season (control structures), I noticed a small mistake. In section 4.2.2 (Arrays), there are three examples demonstrating range loop...
**Use of Semaphores** First of all, let me say that this is amazing work correcting 100 Golang code mistakes while writing clean code. Thank you for your hard work. I...
Fixed import path and updated `go.mod`
A summary of mistake 74 with example code