Clarify comment for the goroutines sample (#366)

* Clarify comment for the goroutines sample.

The current comment may be interpreted to say that the output must be
interleaved, when in fact it doesn't have to be (it depends on the order
the goroutines are run). Make the comment more permissive to avoid the
confusion.

Fixes #365

* Fix phrasing in comment
This commit is contained in:
Eli Bendersky 2021-08-30 07:17:25 -07:00 committed by GitHub
parent ac94809b64
commit a9507f5bbb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 6 deletions

View File

@ -1,7 +1,8 @@
# When we run this program, we see the output of the
# blocking call first, then the interleaved output of the
# two goroutines. This interleaving reflects the
# goroutines being run concurrently by the Go runtime.
# blocking call first, then the output of the two
# goroutines. The goroutines' output may be interleaved,
# because goroutines are being run concurrently by the
# Go runtime.
$ go run goroutines.go
direct : 0
direct : 1

7
public/goroutines generated
View File

@ -157,9 +157,10 @@ separate goroutines now. Wait for them to finish
<tr>
<td class="docs">
<p>When we run this program, we see the output of the
blocking call first, then the interleaved output of the
two goroutines. This interleaving reflects the
goroutines being run concurrently by the Go runtime.</p>
blocking call first, then the output of the two
goroutines. The goroutines&rsquo; output may be interleaved,
because goroutines are being run concurrently by the
Go runtime.</p>
</td>
<td class="code leading">