16 Sep
2020
16 Sep
'20
1:32 p.m.
Rainer Deyke wrote:
I vote to CONDITIONALLY ACCEPT Boost.JSON, conditional on the inclusion of code for parsing and serializing boost::json::value as CBOR.
The one interesting decision that needs to be made here is how to handle CBOR byte strings (major type 3), as they aren't representable in JSON or in the current boost::json::value. I see that Niels Lohmann has added a "binary" 'kind' to the json value for this purpose. Which would then invite the opposite question, what's a JSON serializer supposed to do with kind_binary.