Files
json/docs/mkdocs/docs/api/basic_json/get_ref.md
T
Niels Lohmann 77acd4563c Add element access, iteration, values, and JSON pointers to json_view
Give basic_json_view the read-only access functions of basic_json:
operator[] and at() with keys and indices, front()/back(), find(),
contains(), count(), begin()/end() and cbegin()/cend(), items()
with structured bindings from C++17 on, and type_name().

Exceptions have the ids and messages of the const functions of
basic_json. Where basic_json has undefined behavior the view
answers safely: operator[] with a missing key or an out-of-range
index returns a discarded view, and front()/back() of an empty
container throw invalid_iterator.214. Objects are iterated in
document order, and all members are visited; duplicate-key lookups
find the first member (as yyjson and simdjson do), while parse(),
materialize(), and the map conversions keep the last value, as
parse() does. Keys of up to 16 bytes are compared with two
overlapping loads.

Add value conversions: get<T>()/get_to() for arithmetic types,
bool, nullptr_t, strings (std::basic_string copied,
string_view_t without a copy), BasicJsonType, views, std::vector,
and maps with string keys; get_string() for the string without a
copy; number_token() for the number exactly as written in the
source; value() with keys and JSON pointers; and operator[]/at()/
contains() with JSON pointers. Everything else, including types
with from_json(), goes through materialize() of that subtree.
get<T>() of arithmetic types is inlined down to the conversion, so
reading an integer needs no call.

detail::json_pointer_access exposes a pointer's reference tokens
to code outside basic_json.

Signed-off-by: Niels Lohmann <mail@nlohmann.me>
2026-10-07 16:42:26 +02:00

1.9 KiB

nlohmann::basic_json::get_ref

template<typename ReferenceType>
ReferenceType get_ref();

template<typename ReferenceType>
const ReferenceType get_ref() const;

Implicit reference access to the internally stored JSON value. No copies are made.

Template parameters

ReferenceType
reference type; must be a reference to array_t, object_t, string_t, boolean_t, number_integer_t, or number_unsigned_t, number_float_t, or binary_t. Enforced by a static assertion.

Return value

reference to the internally stored JSON value if the requested reference type fits to the JSON value; throws type_error.303 otherwise

Exception safety

Strong exception safety: if an exception occurs, the original value stays intact.

Exceptions

Throws type_error.303 if the requested reference type does not match the stored JSON value type; example: "incompatible ReferenceType for get_ref, actual type is binary".

Complexity

Constant.

Notes

!!! danger "Undefined behavior"

The reference becomes invalid if the underlying JSON object changes.

Examples

??? example

The example shows several calls to `get_ref()`.

```cpp
--8<-- "examples/get_ref.cpp"
```

Output:

```json
--8<-- "examples/get_ref.output"
```

See also

  • get_ptr() get a pointer value
  • basic_json_view::get_string - the closest counterpart on a zero-copy view: a string without a copy, but as a view rather than a reference to a value that must already exist

Version history

  • Added in version 1.1.0.
  • Extended to binary types in version 3.8.0.