From: Christian Himpel <chressie@googlemail.com>
Date: Mon, 12 Nov 2012 15:25:54 +0000 (-0800)
Subject: faq: mention go vet in "What happens with closures running as goroutines?"
X-Git-Tag: go1.1rc2~1900
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=89ed40c44bf6818ec76108b95cf9268d88ca156b;p=gostls13.git

faq: mention go vet in "What happens with closures running as goroutines?"

R=r
CC=golang-dev
https://golang.org/cl/6822111
---

diff --git a/doc/go_faq.html b/doc/go_faq.html
index 65445d4220..69296bc27b 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -1262,6 +1262,8 @@ each iteration of the loop uses the same instance of the variable <code>v</code>
 each closure shares that single variable. When the closure runs, it prints the 
 value of <code>v</code> at the time <code>fmt.Println</code> is executed,
 but <code>v</code> may have been modified since the goroutine was launched. 
+To help detect this and other problems before they happen, run
+<a href="http://golang.org/cmd/go/#Run_go_tool_vet_on_packages"><code>go vet</code></a>.
 </p>
 
 <p>