Hi,
I've read this topic which helped me a lot:
https://groups.google.com/forum/#!searchin/protobuf/arm%7Csort:date/protobuf/BbYvBRqQyUQ/XHrCGz2cBQAJ
Previously, I tried to build 3.5.0, then I meet the js_embed error.
According to the suggestion given by the above topic, I tried some older
ver
I saw this at
https://developers.google.com/protocol-buffers/docs/proto#updating
Changing a default value is generally OK, as long as you remember that
default values are never sent over the wire. Thus, if a program receives a
message in which a particular field isn't set, the program will see
On Mon, Jan 22, 2018 at 3:08 PM, Ashwin Kini wrote:
> Hi all,
>
> While defining messages can the *tags *be non continous? The
> documentation never mentions the same
>
> message abc {
> optional uint32 xyz = *100*;
> optional uint32 def = *200*;
> optional unit32 abc = *0xDEAD01*;
>
> }
>
> The
Yes, tags (field numbers) can be non-contiguous.
Yes, hex is accepted by protoc
No, repeated fields cannot be required
On 22 January 2018 at 23:08, Ashwin Kini wrote:
> Hi all,
>
> While defining messages can the *tags *be non continous? The
> documentation never mentions the same
>
> message
Hi all,
While defining messages can the *tags *be non continous? The documentation
never mentions the same
message abc {
optional uint32 xyz = *100*;
optional uint32 def = *200*;
optional unit32 abc = *0xDEAD01*;
}
The documentation says it needs to be unique. Agreed. Can they be non
continou
Depending on what you are trying to do and how, gRPC absolutely requires
protobuf 3.0.0+ to build at least its plugins. The gRPC runtime doesn't
require protobuf 3.0.0+, but the plugins do.
On Sunday, January 21, 2018 at 11:44:41 PM UTC-8, mayank yadav wrote:
>
> We are not able to compile the g
