j3d1/json
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

📝 updated documentation wrt. objects #963

Browse source
This commit is contained in:
Niels Lohmann 2018-02-09 23:37:20 +01:00
parent addbbbe136
commit 865ff00de0
No known key found for this signature in database
GPG key ID: 7F3CEA63AE251B69
2 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
include/nlohmann/json.hpp
View file

@ -420,10 +420,10 @@ class basic_json
- When all names are unique, objects will be interoperable in the sense - When all names are unique, objects will be interoperable in the sense
that all software implementations receiving that object will agree on that all software implementations receiving that object will agree on
the name-value mappings. the name-value mappings.
- When the names within an object are not unique, later stored name/value - When the names within an object are not unique, it is unspecified which
pairs overwrite previously stored name/value pairs, leaving the used one of the values for a given key will be chosen. For instance,
names unique. For instance, `{"key": 1}` and `{"key": 2, "key": 1}` will `{"key": 2, "key": 1}` could be equal to either `{"key": 1}` or
be treated as equal and both stored as `{"key": 1}`. `{"key": 2}`.
- Internally, name/value pairs are stored in lexicographical order of the - Internally, name/value pairs are stored in lexicographical order of the
names. Objects will also be serialized (see @ref dump) in this order. names. Objects will also be serialized (see @ref dump) in this order.
For instance, `{"b": 1, "a": 2}` and `{"a": 2, "b": 1}` will be stored For instance, `{"b": 1, "a": 2}` and `{"a": 2, "b": 1}` will be stored

8
single_include/nlohmann/json.hpp
View file

@ -10012,10 +10012,10 @@ class basic_json
- When all names are unique, objects will be interoperable in the sense - When all names are unique, objects will be interoperable in the sense
that all software implementations receiving that object will agree on that all software implementations receiving that object will agree on
the name-value mappings. the name-value mappings.
- When the names within an object are not unique, later stored name/value - When the names within an object are not unique, it is unspecified which
pairs overwrite previously stored name/value pairs, leaving the used one of the values for a given key will be chosen. For instance,
names unique. For instance, `{"key": 1}` and `{"key": 2, "key": 1}` will `{"key": 2, "key": 1}` could be equal to either `{"key": 1}` or
be treated as equal and both stored as `{"key": 1}`. `{"key": 2}`.
- Internally, name/value pairs are stored in lexicographical order of the - Internally, name/value pairs are stored in lexicographical order of the
names. Objects will also be serialized (see @ref dump) in this order. names. Objects will also be serialized (see @ref dump) in this order.
For instance, `{"b": 1, "a": 2}` and `{"a": 2, "b": 1}` will be stored For instance, `{"b": 1, "a": 2}` and `{"a": 2, "b": 1}` will be stored