From: Russ Cox <rsc@golang.org>
Date: Wed, 7 Mar 2012 16:38:39 +0000 (-0500)
Subject: doc: update Effective Go init section
X-Git-Tag: weekly.2012-03-13~137
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=e8d1852d6a46caf5d7a00642dd9abf75b5a28098;p=gostls13.git

doc: update Effective Go init section

Goroutines are no longer excluded from init.

Fixes #3232.

R=golang-dev, gri
CC=golang-dev
https://golang.org/cl/5764044
---

diff --git a/doc/effective_go.html b/doc/effective_go.html
index b9e62b6db4..acca1e5e0d 100644
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -1761,10 +1761,7 @@ var (
 <p>
 Finally, each source file can define its own niladic <code>init</code> function to
 set up whatever state is required.  (Actually each file can have multiple
-<code>init</code> functions.) The only restriction is that, although
-goroutines can be launched during initialization, they will not begin
-execution until it completes; initialization always runs as a single thread
-of execution.
+<code>init</code> functions.)
 And finally means finally: <code>init</code> is called after all the
 variable declarations in the package have evaluated their initializers,
 and those are evaluated only after all the imported packages have been