I saw the start\end group but I couldn't find any information on those and
how to use them.
Your point about skipping fields makes sense.
I think it is also solvable with applying the same idea of chunked
encoding, even on sub fields.
So instead of writing the full length of the child field,
>
> Hm, I think you may have misunderstood me. GOPATH seems to be some
> variable to control the paths searched by the Go language compiler
>
> Yes, it's true. I was in golang context, I looked in the source at
github. Im not familar with this but i think that rel paths from the file
On Wednesday, March 30, 2016 at 2:12:46 AM UTC+2, Horst Noreick wrote:
>
> the compiler uses GOPATH from environment
>
Hm, I think you may have misunderstood me. GOPATH seems to be some variable
to control the paths searched by the Go language compiler.
What I'm looking for is a way to
protos are also gaining "Well-known Types", some of which are "boxed"
(Message) versions of the primitive
types:
https://developers.google.com/protocol-buffers/docs/reference/google.protobuf
I believe the actual docs on well-known types are currently Google-internal
:-(
Zellyn
On Saturday,
Currently this isn't supported by the C# protobuf library. There's a Github
issue for supporting DynamicMessage - which is basically what you'd want -
here: https://github.com/google/protobuf/issues/658
It's unlikely that we'll be supporting this for the initial GA release, but
the more we
