Adds unmodified source files from golang.org.

Adds unmodified source files from golang.org.

BUG=#461
R=jamesr@chromium.org, jamesr

This initial patch contains unmodified source. In the next
patch I will make a small change to one of the files. This is needed by the testing infrastructure for the new Mojom parser.

Committed: https://chromium.googlesource.com/external/mojo/+/230010ba9d5e93d9f4d039a45adccc7cd4daadaf

[rudominer, 2015-11-04 22:24:14]

Description was changed from

==========
Adds unomodified source files from golang.org.

BUG=
==========

to

==========
Adds unmodified source files from golang.org.

BUG=#461
==========

[rudominer, 2015-11-04 22:31:45]

Patchset #1 (id:1) has been deleted

[rudominer, 2015-11-04 22:32:16]

Description was changed from

==========
Adds unmodified source files from golang.org.

BUG=#461
==========

to

==========
Adds unmodified source files from golang.org.

BUG=#461
R=jamesr
==========

[rudominer, 2015-11-04 22:32:17]

rudominer@chromium.org changed reviewers:
+ jamesr@chromium.org

[rudominer, 2015-11-04 22:33:53]

Description was changed from

==========
Adds unmodified source files from golang.org.

BUG=#461
R=jamesr
==========

to

==========
Adds unmodified source files from golang.org.

BUG=#461
R=jamesr

This initial patch contains unmodified source. In the next
patch I will make a small change to one of the files. This is needed by the
testing infrastructure for the new Mojom parser.
==========

[rudominer, 2015-11-04 22:34:57]

Hi James,

ptal. I called the readme file README instead of README.chromium. Let me know if
this is what you had in mind.

[jamesr, 2015-11-04 22:39:03]

Seems fine process wise, although forking the 'fmt' package seems a little
strange.

how will other go code consume this version of the 'fmt' package?

[jamesr, 2015-11-04 22:41:21]

lgtm

(missed the button)

[rudominer, 2015-11-04 22:45:27]

On 2015/11/04 22:39:03, jamesr wrote:
> Seems fine process wise, although forking the 'fmt' package seems a little
> strange.
> 
> how will other go code consume this version of the 'fmt' package?

It is easy to consume. It is even easy to consume simultaneously with the real
fmt package.
You simply do something like

import "fmt" // the real fmt package
myfmt import "third_party/golang/src/fmt"

// invoke the real fmt package
fmt.Sprintf(.....)

// invoke the custom fmt package
myfmt.Sprintf(....)

As to why I am doing this:
The fmt package contains a very useful method that uses reflection to deep print
a structure.
Unfortunately the logic of that code only follows pointers one level out of fear
of cycles.
This means that if your structure uses multiple levels of pointers it doesn't
deep print well.
My patch will correct that. It makes some of my unit tests much shorter and
easier to read.

[rudominer, 2015-11-04 22:46:51]

Committed patchset #1 (id:20001) manually as
230010ba9d5e93d9f4d039a45adccc7cd4daadaf (presubmit successful).