mirror of
https://github.com/teivah/100-go-mistakes.git
synced 2026-06-26 19:37:09 +08:00
fix: wording
This commit is contained in:
parent
d09ae18eb6
commit
67bbf2097b
1 changed files with 1 additions and 1 deletions
|
|
@ -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 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.
|
||||
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)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue