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

fix: wording

Browse source
This commit is contained in:
thetnaingtn 2023-10-11 21:11:51 +07:00
parent d09ae18eb6
commit 67bbf2097b
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/index.md
View file

@ -1676,7 +1676,7 @@ When considering the channel size, we should choose 1 as a default channel size,
* When a fixed number of worker goroutines send a data to a shared channel. * When a fixed number of worker goroutines send a data to a shared channel.
* When using channel for rate-limiting problems. * When using channel for rate-limiting problems.
Other than the above mentioned scenarios, you should have a good reason to specify a channel size other than one for buffered channels. Other than the above mentioned scenarios, you should have a good reason to specify a channel size other than one for buffered channels.
A unbuffered channel can slow down the program a bit as compare to buffered channel, since the producer goroutine has to wait until the receiver goroutine ready to accept the message. A unbuffered channel can slow down the program as compare to buffered channel, since the producer goroutine has to wait until the receiver goroutine ready to accept the message.
### Forgetting about possible side effects with string formatting (etcd data race example and deadlock) (#68) ### Forgetting about possible side effects with string formatting (etcd data race example and deadlock) (#68)