Google contributor.

R=golang-dev, iant
CC=golang-dev
https://golang.org/cl/5554084

So it's not included in the package by the go tool.

R=iant, fullung, rsc
CC=golang-dev
https://golang.org/cl/5563049

Document that indirection through a nil pointer will panic.
Explain function invocation.
This section will need more work, but it's a start.

Fixes #1865.
Fixes #2252.

R=rsc, iant, r
CC=golang-dev
https://golang.org/cl/5532114

R=adg, rsc, r
CC=golang-dev
https://golang.org/cl/5562051

Fixes #2674.

R=rsc
CC=golang-dev
https://golang.org/cl/5574045

Fixes #2582

R=rsc
CC=golang-dev
https://golang.org/cl/5574044

R=rsc
CC=golang-dev
https://golang.org/cl/5555071

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5561060

R=rsc, nigeltao
CC=golang-dev
https://golang.org/cl/5561056

R=rsc
CC=golang-dev
https://golang.org/cl/5555070

iant's idea.

Fixes #2745.

R=iant, dsymonds
CC=golang-dev
https://golang.org/cl/5536085

Invaluable when changing template files.

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/5571044

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/5564045

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/5564046

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/5571043

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/5569043

Marshalling of []byte in attributes and the general
marshalling of named []byte types was fixed.

A []byte field also won't be nil if an XML element
was mapped to it, even if the element is empty.

Tests were introduced to make sure that *struct{}
fields works correctly for element presence testing.
No changes to the logic made in that regard.

R=rsc
CC=golang-dev
https://golang.org/cl/5539070

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/5568043

R=adg
CC=golang-dev
https://golang.org/cl/5554073

R=rsc
CC=golang-dev
https://golang.org/cl/5529055

It was 2^31, but that could cause overflow and trouble.
Reduce it to 2^30 and add a TODO.

R=golang-dev, iant
CC=golang-dev
https://golang.org/cl/5562049

I haven't looked at the source, but the gc compiler appears to
omit "not used" errors when there is an error in the
initializer.  This is harder to do in gccgo, and frankly I
think the "not used" error is still useful even if the
initializer has a problem.  This CL tweaks some tests to avoid
the error, which is not the point of these tests in any case.

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

        Their last use is removed in rev 70ed048caad2.

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

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

It takes too much memory to be reliable and causes
trouble on 32-bit machines.
Sigh.

Fixes #2756.

R=golang-dev, bradfitz
CC=golang-dev
https://golang.org/cl/5567043

R=r, dave, r
CC=golang-dev
https://golang.org/cl/5533086

Make the panic detectable, and use that in ioutil.ReadFile to
give an error if the file is too big.

R=golang-dev, minux.ma, bradfitz
CC=golang-dev
https://golang.org/cl/5563045

R=rsc
CC=golang-dev
https://golang.org/cl/5556077

Fixes #2654.

R=rsc
CC=golang-dev
https://golang.org/cl/5545058

R=rsc
CC=golang-dev
https://golang.org/cl/5555066

This fixes the bug Rob ran into when editing package bytes.
Regexp imports regexp/syntax, which imports bytes, and
regexp/syntax was not being properly recompiled during a
test of a change to package bytes.

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

R=rsc, imkrasin
CC=golang-dev
https://golang.org/cl/5554066

This should go in after Brad's CL 5553064.

R=bradfitz, rsc
CC=golang-dev
https://golang.org/cl/5555056

Also: Avoid potential crash due to reslicing of nil buffer.

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

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

R=iant
CC=golang-dev
https://golang.org/cl/5555062

This should make it easier to add the zillion little changes coming.
No content change here beyond a couple of introductory sentences.
Sections have been moved wholesale without editing them.

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

Preserve test.

changeset:   11593:f1deaf35e1d1
user:        Luuk van Dijk <lvd@golang.org>
date:        Tue Jan 17 10:00:57 2012 +0100
summary:     gc: fix infinite recursion for embedded interfaces

This is causing 'interface type loop' errors during compilation
of a complex program.  I don't understand what's happening
well enough to boil it down to a simple test case, but undoing
this change fixes the problem.

The change being undone is fixing a corner case (uses of
pointer to interface in an interface definition) that basically
only comes up in erroneous Go programs.  Let's not try to
fix this again until after Go 1.

Unfixes issue 1909.

TBR=lvd
CC=golang-dev
https://golang.org/cl/5555063

Fixes #2743.

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

Fixes #2748.

R=rsc, r, r
CC=golang-dev
https://golang.org/cl/5557072