When serializing a message with SerializeDelimitedToOstream, is the
expectation that parsing the resulting serial stream will re-sync if some
data is lost (eg, if the serialized stream is sent over a radio modem)?
Some preliminary testing that I did showed that parsing data after some
lost
Hey Alex --
I just posted a reply on the PR. Sorry for the delay.
--dlj
On Wednesday, July 1, 2020 at 12:45:46 PM UTC-7 stackedsax wrote:
> Can I buymeacoffee.com for someone to put a CI label on this PR? Or is
> there somewhere else I should try and reach out to folks?
>
> Cheers,
>
> -Alex
The sources generated by protoc do not vary by platform... protoc isn't a
cross-compiler itself, it's just a source code generator.
The goal would be to get the protoc binary for your build environment, and
use it to generate the sources to feed into your host/target platform.
In other words,
If there's an error, please let us know...
On Friday, April 24, 2020 at 11:55:06 AM UTC-7, omár sweidán wrote:
>
> Hello, Team!
>
> I want to know if a normal human being is able to edit the Developers
> Guide page, even with the supervision of the Google team?
>
--
You received this message
It looks like this:
types: ["1"]
should be:
type: ["1"]
Does that change fix the error?
On Thursday, April 23, 2020 at 7:16:31 PM UTC-7, mustache_master wrote:
>
>
> Can custom option be set to repeated?
>
> sample code
> syntax = "proto3";
>
> package sample;
>
> import
(I think Kerry's reply went to a different thread...)
On Thursday, April 23, 2020 at 5:11:05 PM UTC-7, Crouse, Kerry wrote:
>
> David,
>
> Thank you for your very prompt reply! I am required (for
> compatibility) to use version 2.6.0. I'm not sure this makes much of a
> difference. What I
The fundamental unit for protobufs (across all serialization and
presentation formats, including JSON) is a message.
The semantics of the general JSON format do not map to protobuf semantics
very well, but the proto3 language guide has a section on the JSON
structures that can interoperate
(I'm assuming this is for C++...)
The protobuf libraries (including the code generated by the protobuf
compiler) should internally contain the necessary #ifdef/etc. guards to
handle endian issues. For example:
