[protobuf] Protobuf and Golang: How to generate a map string interface using proto3?

Hi, I am new in using Protobuf for golang. https://github.com/golang/protobuf Using golang Protobuf, within *package **foo*, I created *message TaskJobEntity* which is a combination of other messages: message TaskJobEntity { JobEntity job = 1; TaskEntity task = 2; map

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Adam, I understand there is no *current* plan to deprecate proto2. But is it really expected to be supported forever? If that's the case, I suppose the only reason to choose proto3 over proto2 (if you happen to want the features and semantics of proto2) might be that not all languages/runtimes

Re: [protobuf] setting fields in repeated messages rise exception

My guess is that you're somehow mixing new generated code with an older runtime library. That Internal.checkNotNull method was introduced earlier this year, so older versions of the runtime don't have it. I'm surprised that you got a NoSuchMethodError instead of a compile-time error, though. On

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Yes, we are planning on supporting proto2 pretty much forever. Within Google we have a huge amount of code using proto2 and for the most part we're not attempting to migrate existing code to proto3. Language support is one reason to go with proto3, but it's also simpler and more convenient for

Re: [protobuf] Protobuf and Golang: How to generate a map string interface using proto3?

On Tue, Dec 19, 2017 at 10:01 AM, wrote: > Hi, I am new in using Protobuf for golang. > > https://github.com/golang/protobuf > > > Using golang Protobuf, within *package **foo*, I created *message > TaskJobEntity* which is a combination of other messages: > > > message

[protobuf] Re: Protobuf and Golang: How to generate a map string interface using proto3?

To be clear, what I meant by: "a *proto3* package cannot reference another *proto3* package" To complete that statement, "within the same repository". So, *I am not sure if I can do a local import of a proto3 package*. There are multiple Protobuf packages within this repository, and each

Re: [protobuf] Is protobuf3 a superset of protobuf2?

Actually we have no plans to deprecate proto2 and we are still actively developing it, so you can really choose either one without having to worry about support going away. On Sat, Dec 16, 2017 at 11:42 AM, Josh Humphries wrote: > I think proto3 was intended to be simpler