Reviewed all 1008 GitHub Discussions (2020-2026) for recurring questions that better or more visible documentation would have avoided. Adds/expands documentation for ~26 distinct gaps, including: - New "Debugging" page collecting natvis, GDB pretty printer, LLDB status, and JSON_DIAGNOSTICS pointers (previously scattered/undiscoverable) - Thread-safety and schema-validation FAQ entries - StringType's char-based requirement (no wstring/u16string/u32string) - Brace-initialization-yields-arrays warning directly on the constructor reference page (previously only in the FAQ, missed by users reading the constructor docs) - std::any exclusion from get<T>(), with a manual-dispatch example - Non-string-keyed std::map serializing as an array of pairs - ordered_json compatibility with NLOHMANN_DEFINE_TYPE_* macros (already worked, was undocumented) - std::array truncation on size-mismatched conversion (no exception) - static_cast vs. get<std::optional<T>>() divergence - Recipe for omitting a std::optional field instead of emitting null - No built-in nesting-depth limit during parsing + a callback-based workaround recipe - Recipe for streaming a large homogeneous array via parser callbacks - operator>> stream-position semantics for concatenated JSON values - JSON Pointer array-vs-object creation rule for non-existing paths - CMake target name (nlohmann_json_modules) needed to link C++20 modules - ESP-IDF/PlatformIO: no official package, link to a community fork - get(key, default) as the Python dict.get() equivalent - reserve() recipe for pre-allocating array capacity - JSONC as an alias for the existing ignore_comments/ignore_trailing_commas combination (distinct from the unsupported JSON5) - items() dereferenced-element type: decltype() idiom + detail-namespace stability caveat - Various macro/type-conversion limitations (MSGPACK_DEFINE_ARRAY equivalent, char-array round-tripping, ADL serializer macro gap) Signed-off-by: Niels Lohmann <mail@nlohmann.me>
9.7 KiB
nlohmann::basic_json::operator[]
// (1)
reference operator[](size_type idx);
const_reference operator[](size_type idx) const;
// (2)
reference operator[](typename object_t::key_type key);
const_reference operator[](const typename object_t::key_type& key) const;
// (3)
template<typename KeyType>
reference operator[](KeyType&& key);
template<typename KeyType>
const_reference operator[](KeyType&& key) const;
// (4)
reference operator[](const json_pointer& ptr);
const_reference operator[](const json_pointer& ptr) const;
- Returns a reference to the array element at specified location
idx. - Returns a reference to the object element with specified key
key. The non-const qualified overload takes the key by value. - See 2. This overload is only available if
KeyTypeis comparable with#!cpp typename object_t::key_typeand#!cpp typename object_comparator_t::is_transparentdenotes a type. - Returns a reference to the element with specified JSON pointer
ptr.
Template parameters
KeyType- A type for an object key other than
json_pointerthat is comparable withstring_tusingobject_comparator_t. This can also be a string view (C++17).
Iterator invalidation
For the non-const versions 1. and 4., when passing an array index that does not exist, it is created and filled with
a #!json null value before a reference to it is returned. For this, a reallocation can happen, in which case all
iterators (including the end() iterator) and all references to the elements are invalidated.
For ordered_json, also passing an object key to the non-const versions 2., 3., and 4., a
reallocation can happen which again invalidates all iterators and all references.
Parameters
idx(in)- index of the element to access
key(in)- object key of the element to access
ptr(in)- JSON pointer to the desired element
Return value
- (const) reference to the element at index
idx - (const) reference to the element at key
key - (const) reference to the element at key
key - (const) reference to the element pointed to by
ptr
Exception safety
Strong exception safety: if an exception occurs, the original value stays intact.
Exceptions
- The function can throw the following exceptions:
- Throws
type_error.305if the JSON value is not an array or null; in that case, using the[]operator with an index makes no sense.
- Throws
- The function can throw the following exceptions:
- Throws
type_error.305if the JSON value is not an object or null; in that case, using the[]operator with a key makes no sense.
- Throws
- See 2.
- The function can throw the following exceptions:
- Throws
parse_error.106if an array index in the passed JSON pointerptrbegins with '0'. - Throws
parse_error.109if an array index in the passed JSON pointerptris not a number. - Throws
out_of_range.402if the array index '-' is used in the passed JSON pointerptrfor the const version. - Throws
out_of_range.404if the JSON pointerptrcan not be resolved. - Throws
out_of_range.410if an array index in the passed JSON pointerptrexceeds the range ofsize_type(e.g., on 32-bit platforms).
- Throws
Complexity
- Constant if
idxis in the range of the array. Otherwise, linear inidx - size(). - Logarithmic in the size of the container.
- Logarithmic in the size of the container.
- Logarithmic in the size of the container.
Notes
!!! danger "Undefined behavior and runtime assertions"
The following cases apply to the **const** overloads; the non-const overloads instead insert the missing element
(see the notes below).
1. If the element at index `idx` does not exist, the behavior is undefined.
2. If the element with key `key` does not exist, the behavior is undefined and is **guarded by a
[runtime assertion](../../features/assertions.md)**!
-
The non-const version may add values: If
idxis beyond the range of the array (i.e.,idx >= size()), then the array is silently filled up with#!json nullvalues to makeidxa valid reference to the last stored element. In case the value was#!json nullbefore, it is converted to an array. -
If
keyis not found in the object, then it is silently added to the object and filled with a#!json nullvalue to makekeya valid reference. In case the value was#!json nullbefore, it is converted to an object. -
See 2.
-
nullvalues are created in arrays and objects if necessary.In particular:
- If the JSON pointer points to an object key that does not exist, it is created and filled with a
#!json nullvalue before a reference to it is returned. - If the JSON pointer points to an array index that does not exist, it is created and filled with a
#!json nullvalue before a reference to it is returned. All indices between the current maximum and the given index are also filled with#!json null. - The special value
-is treated as a synonym for the index past the end.
!!! note "Creating intermediate levels that don't exist yet"
When the JSON pointer traverses intermediate levels that don't exist at all yet (not just a missing leaf), each missing level is created as an array or an object depending on whether the corresponding pointer token parses as a non-negative integer: a numeric token creates an array, a non-numeric token creates an object. For example, on an initially `#!json null` value, `/foo/0/0/0` creates nested arrays, while `/foo/one/one/one` creates nested objects. This is not specified by the JSON Pointer RFC; it is this library's own, intentional disambiguation rule. See also [JSON Pointer](../../features/json_pointer.md). - If the JSON pointer points to an object key that does not exist, it is created and filled with a
Examples
??? example "Example: (1) access specified array element"
The example below shows how array elements can be read and written using `[]` operator. Note the addition of
`#!json null` values.
```cpp
--8<-- "examples/operator_array__size_type.cpp"
```
Output:
```json
--8<-- "examples/operator_array__size_type.output"
```
??? example "Example: (1) access specified array element (const)"
The example below shows how array elements can be read using the `[]` operator.
```cpp
--8<-- "examples/operator_array__size_type_const.cpp"
```
Output:
```json
--8<-- "examples/operator_array__size_type_const.output"
```
??? example "Example: (2) access specified object element"
The example below shows how object elements can be read and written using the `[]` operator.
```cpp
--8<-- "examples/operator_array__object_t_key_type.cpp"
```
Output:
```json
--8<-- "examples/operator_array__object_t_key_type.output"
```
??? example "Example: (2) access specified object element (const)"
The example below shows how object elements can be read using the `[]` operator.
```cpp
--8<-- "examples/operator_array__object_t_key_type_const.cpp"
```
Output:
```json
--8<-- "examples/operator_array__object_t_key_type_const.output"
```
??? example "Example: (3) access specified object element using string_view"
The example below shows how object elements can be read using the `[]` operator.
```cpp
--8<-- "examples/operator_array__keytype.c++17.cpp"
```
Output:
```json
--8<-- "examples/operator_array__keytype.c++17.output"
```
??? example "Example: (3) access specified object element using string_view (const)"
The example below shows how object elements can be read using the `[]` operator.
```cpp
--8<-- "examples/operator_array__keytype_const.c++17.cpp"
```
Output:
```json
--8<-- "examples/operator_array__keytype_const.c++17.output"
```
??? example "Example: (4) access specified element via JSON Pointer"
The example below shows how values can be read and written using JSON Pointers.
```cpp
--8<-- "examples/operator_array__json_pointer.cpp"
```
Output:
```json
--8<-- "examples/operator_array__json_pointer.output"
```
??? example "Example: (4) access specified element via JSON Pointer (const)"
The example below shows how values can be read using JSON Pointers.
```cpp
--8<-- "examples/operator_array__json_pointer_const.cpp"
```
Output:
```json
--8<-- "examples/operator_array__json_pointer_const.output"
```
See also
- documentation on unchecked access
- documentation on runtime assertions
- see
atfor access by reference with range checking - see
valuefor access with default value
Version history
- Added in version 1.0.0.
- Added in version 1.0.0. Added overloads for
T* keyin version 1.1.0. Removed overloads forT* key(replaced by 3) in version 3.11.0. - Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept
std::string_view-convertible keys, as already supported byat,value,find, and other lookup functions. - Added in version 2.0.0.