qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-21 19:34:46 -07:00
Code Releases Activity

spec: define that initialization is sequential

Browse Source 
This is true of the existing implementations, and I think
it is an important property to guarantee.

R=golang-dev, r, borman, r
CC=golang-dev
https://golang.org/cl/5321058
This commit is contained in:
Russ Cox 2011-10-27 12:22:45 -07:00
parent fd31d9fd7b
commit b7ef3c9a54
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/go_spec.html
View File

@ -5149,12 +5149,22 @@ func main() { … }
<p> <p>
Program execution begins by initializing the main package and then Program execution begins by initializing the main package and then
invoking the function <code>main</code>. invoking the function <code>main</code>.
</p>
<p>
When the function <code>main</code> returns, the program exits. When the function <code>main</code> returns, the program exits.
It does not wait for other (non-<code>main</code>) goroutines to complete. It does not wait for other (non-<code>main</code>) goroutines to complete.
</p> </p>
<p>
Package initialization&mdash;variable initialization and the invocation of
<code>init</code> functions&mdash;happens in a single goroutine,
sequentially, one package at a time.
An <code>init</code> function may launch other goroutines, which can run
concurrently with the initialization code. However, initialization
always sequences
the <code>init</code> functions: it will not start the next
<code>init</code> until
the previous one has returned.
</p>
<h2 id="Run_time_panics">Run-time panics</h2> <h2 id="Run_time_panics">Run-time panics</h2>
<p> <p>