XeLabs/100-go-mistakes
2
0
Fork 0
mirror of https://github.com/teivah/100-go-mistakes.git synced 2026-06-21 00:47:11 +08:00
Code Issues Projects Releases Packages Wiki Activity

Update README.md

Browse source
This commit is contained in:
Teiva Harsanyi 2023-06-07 12:39:05 +02:00 committed by GitHub
parent 570f556103
commit 38ee54565f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -139,7 +139,7 @@ This section contains a summary of the 100 mistakes in the book. Meanwhile, it's
* [Not using testing utility packages](#not-using-testing-utility-packages-httptest-and-iotest-88)
* [Writing inaccurate benchmarks](#writing-inaccurate-benchmarks-89) ([Read the full excerpt 👀](https://teivah.medium.com/how-to-write-accurate-benchmarks-in-go-4266d7dd1a95))
* [Not exploring all the Go testing features](#not-exploring-all-the-go-testing-features-90)
* [Not using fuzzing](#not-using-fuzzing-community-mistake) (community mistake, credits: [@jeromedoucet](https://github.com/jeromedoucet))
* [Not using fuzzing](#not-using-fuzzing-community-mistake) (community mistake)
* [Optimizations](#optimizations)
* [Not understanding CPU caches](#not-understanding-cpu-caches-91)
* [Writing concurrent code that leads to false sharing](#writing-concurrent-code-that-leads-to-false-sharing-92)
@ -608,7 +608,7 @@ The `iotest` package helps write io.Reader and test that an application is toler
You can use setup and teardown functions to configure a complex environment, such as in the case of integration tests.
#### Not using fuzzing (community mistake)
#### Not using fuzzing (community mistake, credits: [@jeromedoucet](https://github.com/jeromedoucet))
Fuzzing is an efficient strategy to detect random, unexpected, or malformed inputs to complex functions and methods in order to discover vulnerabilities, bugs, or even potential crashes.