(Oops, your emails weren't going through from this address because they
were landing in the Google Groups moderation queue. I just went and cleared
it out (resulting in these dupes, sorry) and allowlisted this address so it
won't be moderated in the future.)
-Kenton
On Mon, Oct 17, 2022 at 12:08
I took the initiative to add/restore the Cap'n Proto line.
Please tell me if anything is wrong of if more links/references are needed.
Thanks
Christophe
Le vendredi 30 septembre 2022 à 01:49:22 UTC+2, ken...@cloudflare.com a
écrit :
> It used to be there, but someone removed it, with the comme
I took the initiative to restore the Cap'n Proto line. Please tell me if
anything is wrong or if you want me to add references.
Thanks
Christophe
Le vendredi 30 septembre 2022 à 01:49:22 UTC+2, ken...@cloudflare.com a
écrit :
> It used to be there, but someone removed it, with the comment "clea
Thanks again Ken !
One step at a time... Seems I'm now falling in the trap described
here: https://groups.google.com/g/capnproto/c/9J_AOQzSEbU/m/qpuEjQXhBAAJ
So I'm wondering now if there is an available example of C++ implementation
of a RPC schema using inheritance, similar to the Calculator
Done.
I can eventually add your phrase below as a note. What do you think ?
Christophe
> Le 17 oct. 2022 à 16:14, Kenton Varda a écrit :
>
> Thanks.
>
> FWIW I'd argue that Cap'n Proto should have a "no" under "Supports
> references?". Although the binary encoding uses pointers, implementatio
Thanks.
FWIW I'd argue that Cap'n Proto should have a "no" under "Supports
references?". Although the binary encoding uses pointers, implementations
generally forbid the message structure to be anything other than
tree-shaped. You're not supposed to ever have multiple pointers pointing at
the same
