Joe Tsai

`google.golang.org/protobuf/protoadapt`?

In addition to concerns about duplication of this same messaging on every generated message, I suspect that most calls to the `String` method do not happen directly, but indirectly through...

> It should, but I don't think this need to block v2. Agreed.

> I‘m not sure about reinforcing a habit of unmarshalling const string into a proto message for initialization True, I'm not fond of having multiple ways of doing the same...

> I have just had to abandon an upgrade because we copy messages. Because they now contain mutexes the copylocks check of the go vet command now fails in numerous...

This appears to be a bug in the C++ code. The Go protobuf implementation does not link in any of the C++ code. From the release notes, it's unclear to...

One problem with the `optimize_for` file option is that it assumes that the owner of a given `.proto` file is the best team to decide how the generated code should...

\cc @randall77 @LMMilewski

I should mention that the `net` package uses an `io.Reader` along with type assertions to achieve this behavior. See golang/go#17607 and [`net.Buffers`](https://golang.org/pkg/net#Buffers).

goroutines are certainly cheap, but not so cheap that you would want to spawn one for every unmarshal operation and deal with the synchronization. In Go, the standard library only...