| commit | 5df7130c3b2876c9a841c9aa80c06726369e3f6d | [log] [tgz] |
|---|---|---|
| author | shulhan <m.shulhan@gmail.com> | Wed Dec 30 02:19:41 2020 +0700 |
| committer | Andrew Gerrand <adg@golang.org> | Mon Jan 04 23:28:05 2021 +0000 |
| tree | 9ea16b5f47b8ce062e3c083c0163a0303018e49d | |
| parent | e47ccffc4b7abf7e0548ca3dff2fce54d6f584a4 [diff] |
[x/blog] content: fix line numbers on output of Timer.Reset example
From perspective of someone who may not or may have an experience on
having race conditions, the line number "15" a little bit off because it
does not have any reference to variable `t`.
Especially when the next paragraph said "The race detector shows the
problem: an unsynchronized read and write of the variable t".
This changes not only fix the line number "15", but also make it
consistent with actual output (although its run on Go tip not Go 1.1),
----
% go run -race race.go
950.434733ms
==================
WARNING: DATA RACE
Read at 0x00c00013e018 by goroutine 8:
main.main.func1()
race.go:14 +0x126
Previous write at 0x00c00013e018 by main goroutine:
main.main()
race.go:12 +0x194
Goroutine 8 (running) created at:
time.goFunc()
.../share/go/src/time/sleep.go:169 +0x51
==================
1.037465812s
1.706961927s
...
----
the read conflict is on `func 001` (line number 16 on example) and write
conflict is on main (line number 14 on example).
Change-Id: I3b9a7880178845d8dc4dff38e197fc3eef407e58
Reviewed-on: https://go-review.googlesource.com/c/blog/+/280712
Reviewed-by: Andrew Gerrand <adg@golang.org>
X-Blog-Commit: c2ef14610cd691addcce190e8998df47bdb8c002
This repository holds the Go Website server code and content.
The easiest way to install is to run go get -u golang.org/x/website. You can also manually git clone the repository to $GOPATH/src/golang.org/x/website.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the time repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.