From 48ba6fe553a5480de8a5fd6da1ab7709c0becc3b Mon Sep 17 00:00:00 2001 From: Andrew Gerrand Date: Fri, 4 Oct 2013 09:45:06 +1000 Subject: [PATCH] doc: move spec and memory model back to /ref/ R=golang-dev, r CC=golang-dev https://golang.org/cl/14364043 --- doc/articles/wiki/index.html | 4 ++-- doc/docs.html | 4 ++-- doc/effective_go.html | 6 +++--- doc/go1.1.html | 6 +++--- doc/go_faq.html | 8 ++++---- doc/go_mem.html | 2 +- doc/go_spec.html | 2 +- 7 files changed, 16 insertions(+), 16 deletions(-) diff --git a/doc/articles/wiki/index.html b/doc/articles/wiki/index.html index ed42e3981e..f57857a7f3 100644 --- a/doc/articles/wiki/index.html +++ b/doc/articles/wiki/index.html @@ -154,7 +154,7 @@ function to return *Page and error. Callers of this function can now check the second parameter; if it is nil then it has successfully loaded a Page. If not, it will be an error that can be handled by the caller (see the -language specification for details). +language specification for details).

@@ -616,7 +616,7 @@ Let's put a call to getTitle in each of the handlers: Catching the error condition in each handler introduces a lot of repeated code. What if we could wrap each of the handlers in a function that does this validation and error checking? Go's -function +function literals provide a powerful means of abstracting functionality that can help us here.

diff --git a/doc/docs.html b/doc/docs.html index 8c5d17a64a..7aad8dadf4 100644 --- a/doc/docs.html +++ b/doc/docs.html @@ -85,12 +85,12 @@ The documentation for the Go standard library. The documentation for the Go tools.

-

Language Specification

+

Language Specification

The official Go Language specification.

-

The Go Memory Model

+

The Go Memory Model

A document that specifies the conditions under which reads of a variable in one goroutine can be guaranteed to observe values produced by writes to the diff --git a/doc/effective_go.html b/doc/effective_go.html index 6e7ee1a28e..7eceac5d82 100644 --- a/doc/effective_go.html +++ b/doc/effective_go.html @@ -27,7 +27,7 @@ will be easy for other Go programmers to understand.

This document gives tips for writing clear, idiomatic Go code. -It augments the language specification, +It augments the language specification, the Tour of Go, and How to Write Go Code, all of which you @@ -709,7 +709,7 @@ Erroneous encodings consume one byte and produce the replacement rune U+FFFD. (The name (with associated builtin type) rune is Go terminology for a single Unicode code point. -See the language specification +See the language specification for details.) The loop

@@ -2969,7 +2969,7 @@ func Serve(queue chan *Request) {

Because data synchronization occurs on a receive from a channel (that is, the send "happens before" the receive; see -The Go Memory Model), +The Go Memory Model), acquisition of the semaphore must be on a channel receive, not a send.

diff --git a/doc/go1.1.html b/doc/go1.1.html index 84fb372569..a68664954a 100644 --- a/doc/go1.1.html +++ b/doc/go1.1.html @@ -81,7 +81,7 @@ See the Unicode section for more information.

Go 1.1 now implements -method values, +method values, which are functions that have been bound to a specific receiver value. For instance, given a Writer @@ -129,7 +129,7 @@ only an infinite "for" loop.

In Go 1.1, the rule about final "return" statements is more permissive. It introduces the concept of a -terminating statement, +terminating statement, a statement that is guaranteed to be the last one a function executes. Examples include "for" loops with no condition and "if-else" @@ -191,7 +191,7 @@ more than 2 billion elements on 64-bit platforms. Updating: Most programs will be unaffected by this change. Because Go does not allow implicit conversions between distinct -numeric types, +numeric types, no programs will stop compiling due to this change. However, programs that contain implicit assumptions that int is only 32 bits may change behavior. diff --git a/doc/go_faq.html b/doc/go_faq.html index d36080ff07..f65dff7964 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -68,7 +68,7 @@ Go became a public open source project on November 10, 2009. After a couple of years of very active design and development, stability was called for and Go 1 was released on March 28, 2012. -Go 1, which includes a language specification, +Go 1, which includes a language specification, standard libraries, and custom tools, provides a stable foundation for creating reliable products, projects, and publications. @@ -1278,7 +1278,7 @@ What operations are atomic? What about mutexes?

We haven't fully defined it all yet, but some details about atomicity are -available in the Go Memory Model specification. +available in the Go Memory Model specification.

@@ -1334,7 +1334,7 @@ will experience performance degradation when using multiple OS threads. This is because sending data between threads involves switching contexts, which has significant cost. -For instance, the prime sieve example +For instance, the prime sieve example from the Go specification has no significant parallelism although it launches many goroutines; increasing GOMAXPROCS is more likely to slow it down than to speed it up. @@ -1357,7 +1357,7 @@ is not Parallelism. Why do T and *T have different method sets?

-From the Go Spec: +From the Go Spec:

diff --git a/doc/go_mem.html b/doc/go_mem.html index d2cbd3eacc..3e769daeca 100644 --- a/doc/go_mem.html +++ b/doc/go_mem.html @@ -1,7 +1,7 @@