I changed the encoding so that the previous generated code is no longer
necessary. Encoded data now carries all the information needed to decode
struct fields correctly, even if fields have been added and reordered.
On Sunday, January 24, 2021 at 8:29:58 AM UTC-5 Jonathan Amsterdam wrote:
> Th
Thanks for the suggestions. I created https://github.com/jba/codec/pull/1
to address them. You can comment in more detail there if you'd like.
On Wed, Jan 20, 2021 at 12:13 PM roger peppe wrote:
> On Wed, 20 Jan 2021 at 13:31, Jonathan Amsterdam
> wrote:
>
>> The encoding scheme is described br
On Wed, 20 Jan 2021 at 13:31, Jonathan Amsterdam
wrote:
> The encoding scheme is described briefly in the README[0] and the code[1].
>
> To answer your two specific questions, interfaces are represented as a
> pair (typeNumber, value) where typeNumber maps to a registered type. (Like
> gob, types
The encoding scheme is described briefly in the README[0] and the code[1].
To answer your two specific questions, interfaces are represented as a pair
(typeNumber, value) where typeNumber maps to a registered type. (Like gob,
types must be registered.) Structs are represented as: startCode
(fieldN
This is interesting, thanks! Is there a full description of the encoding
somewhere? (e.g. how are structs represented? what about interface values,
etc? is the schema implicit or sent on the wire?)
cheers,
rog.
On Tue, 19 Jan 2021 at 14:59, Jonathan Amsterdam
wrote:
> Uses code generation
Uses code generation for fast encoding and decoding of Go values to bytes.
Handles sharing and cycles too.
https://pkg.go.dev/github.com/jba/codec
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receivin
