x/clean-go-article
1
0
Fork 0
mirror of https://github.com/Pungyeon/clean-go-article.git synced 2024-11-23 14:14:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #7 from prestonvanloon/patch-1

Browse source 
Rename worker_id to workerID
This commit is contained in:
Lasse Martin Jakobsen 2019-06-24 10:13:44 +02:00 committed by GitHub
parent f79eac25ad fa4edd091d
commit 91408d1ed8
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

@ -91,8 +91,8 @@ Now we understand <em>why</em> we have a loop and can tell <em>what</em> we're d
This still isn't what I'd consider clean code. The comment is worrying because it probably should not be necessary to express such an explanation in prose, assuming the code is well written (which it isn't). Technically, we're still saying what we're doing, not why we're doing it. We can easily express this "what" directly in our code by using more meaningful names:
```go
for worker_id := 0; worker_id < 10; worker_id++ {
instantiateThread(worker_id)
for workerID := 0; workerID < 10; workerID++ {
instantiateThread(workerID)
}
```