First of all, congrats on this great little library! I've been looking for a lightweight modern implementation for a while now, really happy to finally have found it.
The only thing that I was a bit irritated by was that there isn't any support for int64 and uint32 / 64 types.
Json doesn't make that distinction, but if you want a non-float value that is larger than 32 bits, or an unsigned int without loosing the values from 1 << 15 and beyond, then you currently have to go through double, which seems odd.
The simple solution could be to internally store all such values as long (in a new JsonLong class), not int, and then do the casting in int_value(), long_value() uint_value() (or unsigned_int_value() if you like it verbose), ulong_value(), ...) But I guess this would still cause troubles when exporting, as it will have to be known if a value was signed or unsigned.
First of all, congrats on this great little library! I've been looking for a lightweight modern implementation for a while now, really happy to finally have found it.
The only thing that I was a bit irritated by was that there isn't any support for int64 and uint32 / 64 types.
Json doesn't make that distinction, but if you want a non-float value that is larger than 32 bits, or an unsigned int without loosing the values from 1 << 15 and beyond, then you currently have to go through double, which seems odd.
The simple solution could be to internally store all such values as long (in a new JsonLong class), not int, and then do the casting in int_value(), long_value() uint_value() (or unsigned_int_value() if you like it verbose), ulong_value(), ...) But I guess this would still cause troubles when exporting, as it will have to be known if a value was signed or unsigned.