Krystian Stasiowski
Krystian Stasiowski
The only normative requirement we don't comply with is checking for duplicate object key. There is some normative encouragements in there that we don't strictly follow, such as limiting precision.
@vinniefalco To conform to I-JSON we would have the check for duplicate keys within `basic_parser`, not the handler.
We can eventually transition `serializer` to use the same `const_stream` as `basic_parser` and then remove the old versions.
The Dimov opinion: Try xxhash32/64
Peter has settled on murmur2
@grisumbras @vinniefalco is correct -- creating the local streams allows for the compiler to assume no aliasing. Without them, it must operate under the assumption that the referenced stream may...
https://develop.json.cpp.al/json/usage/conversion.html > The library provided overloads have no special prioritization over those provided by the user, so care should be taken to avoid writing ambiguous declarations:
Sounds good
@vinniefalco because we use character traits
My only reservation with this PR is that this would result in _all_ bytes being copied (regardless of `size()`... @pdimov what do you think?