[bridged from https://fosstodon.org/@foonathan on the fediverse by https://fed.brid.gy/ ]
a) the bitcode is bit-aligned, not byte aligned, so the slice is more awkward than necessary, and
b) the first entry of the type block needs to specify the number of entries in the byte block. This is encoded as a variable length integer. So after you've encoded all the types and now […]
a) the bitcode is bit-aligned, not byte aligned, so the slice is more awkward than necessary, and
b) the first entry of the type block needs to specify the number of entries in the byte block. This is encoded as a variable length integer. So after you've encoded all the types and now […]
DATA(Foo, (int, a), (float, f))
which generates both struct definitions and JSON serialization code of the form:
json_object_begin(out);
json_object_key(out, "a");
json_int(out, foo.a);
json_object_key(out, "b");
json_float(out, foo […]
DATA(Foo, (int, a), (float, f))
which generates both struct definitions and JSON serialization code of the form:
json_object_begin(out);
json_object_key(out, "a");
json_int(out, foo.a);
json_object_key(out, "b");
json_float(out, foo […]
Because a good C++ programmer, can write C++ in any language.
Because a good C++ programmer, can write C++ in any language.