Closed chmike closed 2 months ago
The ditp/idr/low package supports full time range with time offset and even time zone abbreviation encoding/decoding.
If the low level package supports it natively (i.e. low.PutTime...
) I'd suggest using that instead of nsec to demonstrate it
For demonstration, you should also rerun the benchmarks as instructed in the README.
I have applied your change requests and your suggestion to use the full time with tz offset.
But I don't see the point with the time encoding because we end up comparing apples with oranges. It is obviously slower and bigger with the full time encoding.
I did run the benchmark. Do you want me to commit it as well ?
Yes.
Thank you.
The Information Data Representation (IDR) is a work in progress. This code benchmarks the low level encoding/decoding functions to write custom value encoding/decoding.
The ditp/idr/low package supports full time range with time offset and even time zone abbreviation encoding/decoding. For the benchmark I use the same nsec time encoding as benc.