📝 updated documentation wrt. objects #963
This commit is contained in:
		
							parent
							
								
									addbbbe136
								
							
						
					
					
						commit
						865ff00de0
					
				
					 2 changed files with 8 additions and 8 deletions
				
			
		|  | @ -10012,10 +10012,10 @@ class basic_json | |||
|     - When all names are unique, objects will be interoperable in the sense | ||||
|       that all software implementations receiving that object will agree on | ||||
|       the name-value mappings. | ||||
|     - When the names within an object are not unique, later stored name/value | ||||
|       pairs overwrite previously stored name/value pairs, leaving the used | ||||
|       names unique. For instance, `{"key": 1}` and `{"key": 2, "key": 1}` will | ||||
|       be treated as equal and both stored as `{"key": 1}`. | ||||
|     - When the names within an object are not unique, it is unspecified which | ||||
|       one of the values for a given key will be chosen. For instance, | ||||
|       `{"key": 2, "key": 1}` could be equal to either `{"key": 1}` or | ||||
|       `{"key": 2}`. | ||||
|     - Internally, name/value pairs are stored in lexicographical order of the | ||||
|       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 | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue