With JSON_DIAGNOSTICS and JSON_DIAGNOSTIC_POSITIONS, the exceptions of views now carry the same context as those of basic_json: "(/path) " and "(bytes a-b) " in front of the message, in basic_json's format (with JSON_DIAGNOSTICS, no context for the root). Before, views threw without any context, and since get<T>() reads the view directly, conversions had lost even the relative path they used to get through materialize(). The throw helpers of detail/view/errors.hpp take an error_site (document and node; empty without the two macros). Only on the error path, the path is found by descending from the root (pruned by subtree extent before the first edit, a full walk through edited sequences after), and the bytes as materialize() sets them (position_source; a container's end by following the chain of last elements and scanning to the closing brackets). from_json() for views and the strict enum macro put the same context in front through exception_prefix(). Iterators keep their container only under the two macros, for key(). Without the macros, the accessors compile to the same code as before. Tests compare every value's exceptions with those of the parsed or materialized basic_json value, including edited documents; the checks that were disabled under the two macros run again. Signed-off-by: Niels Lohmann <mail@nlohmann.me>
9.5 KiB
nlohmann::basic_json_view::operator[]
// (1)
basic_json_view operator[](string_view_t key) const;
basic_json_view operator[](const char* key) const;
basic_json_view operator[](const string_t& key) const;
// (2)
basic_json_view operator[](size_type idx) const;
template<typename IntegerType>
basic_json_view operator[](IntegerType idx) const;
// (3)
basic_json_view operator[](const json_pointer& ptr) const;
- Returns the value of the object member with key
key— the first one, should the key occur more than once (see the Notes below) — or a discarded view if there is no such member. - Returns the array element at index
idx, or a discarded view ifidxis out of range. The template accepts every integer type except#!cpp booland#!cpp std::size_t(#!cpp int,#!cpp unsigned,#!cpp long,#!cpp std::int64_t, ...) and forwards to thesize_typeoverload, so that an integer argument is not ambiguous between that overload and 1; a negativeidxis out of range. - Returns the value a JSON pointer
ptrrefers to, starting at this value, or a discarded view wherever resolving it further is not possible without inserting into or extending the document (see Return value and Exceptions below).
Parameters
key(in)- object key of the element to access
idx(in)- index of the element to access
ptr(in)- JSON pointer to the element to access
Return value
- the value of the first member with key
key, or a discarded view if no member has this key (or if this view is discarded) - the element at index
idx, or a discarded view if#!cpp idx >= size()oridxis negative (or if this view is discarded) - the value
ptrresolves to, starting at this value, or a discarded view (also if this view is discarded) for exactly the reference tokens where the const overload ofBasicJsonType::operator[]invokes undefined behavior for the same pointer and the same document: an object member that does not exist, or an array index that is out of range
Exception safety
Strong guarantee: there are no changes to the view or the document it refers to.
Exceptions
- Throws
type_error.305if the value is not an object and not discarded — the same exception, with the same message, that the const overload ofBasicJsonType::operator[]throws for a string argument on a non-object value. - Throws
type_error.305if the value is not an array and not discarded — the same exception, with the same message, that the const overload ofBasicJsonType::operator[]throws for a numeric argument on a non-array value. - Throws the same exceptions, with the same messages, that the const overload of
BasicJsonType::operator[]throws for the same pointer and the same document:out_of_range.402if a reference token is#!cpp "-"at an array.out_of_range.404if a reference token cannot be resolved because it is used on a primitive value.parse_error.106if an array index inptrbegins with#!cpp '0'.parse_error.109if an array index inptris not a number.
As for BasicJsonType, with JSON_DIAGNOSTICS these exceptions name the JSON
Pointer path of the value within the document, and with
JSON_DIAGNOSTIC_POSITIONS its bytes in the source text (where
materialize() sets them).
Complexity
- Linear in the number of members: as for
ordered_json, members are compared one after another, in document order, stopping at the first match. Each comparison first checks the key's length — already known from the index, without reading the key bytes — before comparing its content, so a key of a different length thankeyis rejected without touching the source text. Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes constant time on average. - Linear in
idx: elements are skipped one at a time from the first one, since they are not a fixed size in the index (unlikeBasicJsonType's array, which is random-access). Constant if no element of the array is an array or object, since the elements are then adjacent in the index. - Linear in the number of reference tokens of
ptrand, for each token, in the number of members of the object at that level (as 1.) or the index into the array (as 2.).
Notes
Unlike BasicJsonType::operator[], which is undefined behavior (guarded by a
runtime assertion) for a missing key on a const value, this operator returns a
safe, testable result for a missing key or an index out of range: a discarded view, which is
tested with is_discarded.
There is also no non-const overload that inserts a missing key or extends an array — a view never modifies the
document.
!!! info "Chained access"
`#!cpp operator[]` on a [discarded](is_discarded.md) view returns a discarded view and does not throw, so a chain
like `#!cpp v["a"]["b"][0]` is safe even if `"a"` or `"b"` is missing: the first missing step makes the whole
result discarded, which is tested once at the end. Type errors on values that are *not* discarded still throw: a
key on an array or a primitive, or an index on an object or a primitive, is `type_error.305` as for
`BasicJsonType`. [`at`](at.md) still throws for a discarded view, as it does for a missing key.
!!! warning "Duplicate keys: the first member wins"
If the source text has an object with a duplicate key, `#!cpp operator[]` (and [`at`](at.md), [`find`](find.md),
[`contains`](contains.md), [`value`](value.md), and JSON pointer resolution) all resolve to
the *first* member with that key, because a lookup can stop as soon as it finds a match. This is different from
[`materialize()`](materialize.md) (and [`BasicJsonType::parse()`](../basic_json/parse.md)), which replay every
member in order and so keep the *last* value for a repeated key, so `#!cpp v["a"]` and
`#!cpp v.materialize()["a"]` can differ. To get the value `parse()` would give, use
[`materialize()`](materialize.md) or iterate the members with [`items()`](items.md) and keep the last match.
The key hash index of a larger object (128 members or more) leads to the first member of a key as well.
[`begin()`](begin.md)/[`end()`](end.md) and [`items()`](items.md) iterate over *all* members, including
duplicates, in document order. See [Duplicate keys](../../features/json_view.md#duplicate-keys) and
[`size()`](size.md#notes).
!!! info "JSON pointer resolution"
Overload 3 walks `ptr` one reference token at a time, starting at this value, the same way [`at`](at.md) and
[`contains`](contains.md) do. It only ever returns a discarded view where the **const** overload of
`BasicJsonType::operator[]` would be undefined behavior for the same pointer — a missing object member or an
out-of-range array index — and still throws for every other way `ptr` can fail to resolve. See
[`at`](at.md#exceptions) for the checked version, which throws in every case instead, and
[`contains`](contains.md) for a version that never throws.
Examples
??? example "Example: (1)/(2) access specified element"
The example below reads a couple of fields out of a batch of user records without ever materializing a full
`BasicJsonType` value for the batch. `operator[]` is used both to look up an optional object member and to index
into an array — in both cases, a missing value comes back as a discarded view that can be tested with a plain
`#!cpp if`, instead of relying on undefined behavior.
```cpp
--8<-- "examples/basic_json_view__operator[].cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__operator[].output"
```
??? example "Example: (3) access specified element via JSON pointer"
The example below reaches straight into one deeply nested field of a large document with a single JSON pointer,
without ever building a tree for the rest of it, and shows the discarded-view and throwing outcomes of a pointer
that cannot be fully resolved.
```cpp
--8<-- "examples/basic_json_view__operator[]_json_pointer.cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__operator[]_json_pointer.output"
```
See also
at- access specified element with bounds checking (throws instead of returning a discarded view)front,back- access the first or last elementfind,contains- look up a member without throwingBasicJsonType::operator[]- the corresponding function ofbasic_jsonjson_pointer- JSON pointer type used by overload 3
Version history
- Added in version 3.13.0.