Merge branch 'develop' into issue-4378-enum-map-keys

Signed-off-by: Niels Lohmann <mail@nlohmann.me>
2026-10-04 21:50:33 +00:00 · 2026-10-04 12:27:58 +02:00
parent 10cbcd9562 0c4462676d
commit 6f1b7ea59e
624 changed files with 29977 additions and 18781 deletions
@@ -1,3 +1,8 @@
+# The MkDocs 2.0 banners of Material for MkDocs and ProperDocs (via mkdocs-redirects) are printed to stderr, not
+# logged, so they do not affect --strict; silence them anyway.
+export NO_MKDOCS_2_WARNING := true
+export DISABLE_MKDOCS_2_WARNING := true
+
 # serve the site locally
 serve: style_check
 	venv/bin/mkdocs serve
@@ -8,11 +13,17 @@ serve_dirty: style_check
 # This target is used in the CI (ci_test_build_documentation).
 # This target is used by the docset Makefile.
 build: style_check
-	venv/bin/mkdocs build
+	venv/bin/mkdocs build --strict

 style_check:
 	@cd docs ; ../venv/bin/python3 ../scripts/check_structure.py

+# check that all Mermaid diagrams parse (needs Node.js)
+# This target is used in the CI (ci_test_documentation_mermaid).
+check_mermaid:
+	npm ci --prefix scripts/mermaid --ignore-scripts --no-audit --no-fund
+	node scripts/mermaid/check_mermaid.mjs docs
+
 # check the links in the documentation files in docs/mkdocs
 link_check:
 	ENABLED_HTMLPROOFER=true venv/bin/mkdocs build
@@ -96,7 +96,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by

 ## Examples

-??? example
+??? example "Example: (1) reading from a string"

    The example below demonstrates the `accept()` function reading from a string.

@@ -110,6 +110,21 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/accept__string.output"
    ```

+??? example "Example: (2) reading from an iterator pair"
+
+    The example below demonstrates the `accept()` function reading from an iterator pair. Only the first call covers
+    exactly the JSON text; the second one also covers the trailing bytes and is therefore rejected.
+
+    ```cpp
+    --8<-- "examples/accept__iterator_pair.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/accept__iterator_pair.output"
+    ```
+
 ## See also

 - [parse](parse.md) - deserialize from a compatible input
@@ -137,3 +152,5 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -25,7 +25,7 @@ To store objects in C++, a type is defined by the template parameters explained

 ## Notes

-#### Default type
+### Default type

 With the default values for `ArrayType` (`std::vector`) and `AllocatorType` (`std::allocator`), the default value for
 `array_t` is:
@@ -37,7 +37,7 @@ std::vector<
 >
 ```

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the maximum depth of nesting.
@@ -46,7 +46,7 @@ In this class, the array's limit of nesting is not explicitly constrained. Howev
 introduced by the compiler or runtime environment. A theoretical limit can be queried by calling the
 [`max_size`](max_size.md) function of a JSON array.

-#### Storage
+### Storage

 Arrays are stored as pointers in a `basic_json` type. That is, for any access to array values, a pointer of type
 `#!cpp array_t*` must be dereferenced.
@@ -67,6 +67,13 @@ Arrays are stored as pointers in a `basic_json` type. That is, for any access to
    --8<-- "examples/array_t.output"
    ```

+## See also
+
+- [object_t](object_t.md) the type used to store JSON objects
+- [binary_t](binary_t.md) the type used to store binary values
+- [is_array](is_array.md) checks whether the JSON value is an array
+- [max_size](max_size.md) returns the maximum possible number of elements
+
 ## Version history

 - Added in version 1.0.0.
@@ -0,0 +1,53 @@
+# <small>nlohmann::basic_json::</small>as_base_class
+
+```cpp
+json_base_class_t& as_base_class() noexcept;
+const json_base_class_t& as_base_class() const noexcept;
+```
+
+Returns a reference to this object as its custom base class [`json_base_class_t`](json_base_class_t.md). No copy is
+made.
+
+Since `basic_json` derives from `json_base_class_t`, a member of `basic_json` hides any member of the custom base class
+with the same name. This function makes such hidden members accessible again.
+
+## Return value
+
+reference to this object as [`json_base_class_t`](json_base_class_t.md)
+
+## Exception safety
+
+No-throw guarantee: this function never throws exceptions.
+
+## Complexity
+
+Constant.
+
+## Notes
+
+The function is equivalent to `static_cast<json_base_class_t&>(j)` (or `static_cast<const json_base_class_t&>(j)`).
+
+## Examples
+
+??? example
+
+    The example shows how to use `as_base_class` to access members of the custom base class that are hidden by members
+    of `basic_json`.
+    
+    ```cpp
+    --8<-- "examples/as_base_class.cpp"
+    ```
+    
+    Output:
+    
+    ```json
+    --8<-- "examples/as_base_class.output"
+    ```
+
+## See also
+
+- [json_base_class_t](json_base_class_t.md) - type of the custom base class
+
+## Version history
+
+- Added in version 3.13.0.
@@ -92,6 +92,20 @@ Strong exception safety: if an exception occurs, the original value stays intact
 3. Logarithmic in the size of the container.
 4. Logarithmic in the size of the container.

+## Notes
+
+!!! warning "Deprecation"
+
+    Overload (4) also accepts a [`json_pointer`](../json_pointer/index.md) whose template argument is a `basic_json`
+    specialization (e.g., `nlohmann::json_pointer<nlohmann::json>`) instead of a string type. This is deprecated since
+    version 3.11.0 and will be removed in a future major version; use `basic_json::json_pointer` (for `json`,
+    `nlohmann::json_pointer<std::string>`) instead.
+
+    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
+    function.
+
+    See the [migration guide](../../integration/migration_guide.md#json-pointers) for how to update existing code.
+
 ## Examples

 ??? example "Example: (1) access specified array element with bounds checking"
@@ -224,5 +238,7 @@ Strong exception safety: if an exception occurs, the original value stays intact

 1. Added in version 1.0.0.
 2. Added in version 1.0.0.
-3. Added in version 3.11.0.
+3. Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept `std::string_view`-convertible keys, as
+   already supported by [`operator[]`](operator[].md), [`value`](value.md), [`find`](find.md), and other lookup
+   functions.
 4. Added in version 2.0.0.
@@ -99,6 +99,25 @@ basic_json(basic_json&& other) noexcept;
      elements of the pairs are treated as keys and the second elements are as values.
    3. In all other cases, an array is created.
    
+    The following flowchart also takes into account what happens when `type_deduction` is `#!cpp false`, in which case
+    `manual_type` decides between object and array, and an object can only be forced if `init` actually matches rule 2
+    (or is empty):
+
+    ```mermaid
+    flowchart TD
+        A(["initializer_list init"]) --> B{"empty, or every element is a 2-element<br/>array whose first element is a string?"}
+        B -->|"yes"| C{"type_deduction"}
+        B -->|"no"| D{"type_deduction"}
+        C -->|"true"| OBJ["create object"]
+        C -->|"false"| E{"manual_type"}
+        E -->|"object"| OBJ
+        E -->|"array"| ARR["create array"]
+        D -->|"true"| ARR
+        D -->|"false"| F{"manual_type"}
+        F -->|"array"| ARR
+        F -->|"object"| ERR["throw type_error.301"]
+    ```
+
    The rules aim to create the best fit between a C++ initializer list and JSON values. The rationale is as follows:
    
    1. The empty initializer list is written as `#!cpp {}` which is exactly an empty JSON object.
@@ -139,8 +158,8 @@ basic_json(basic_json&& other) noexcept;

    - In case of a `#!json null` type, [invalid_iterator.206](../../home/exceptions.md#jsonexceptioninvalid_iterator206)
      is thrown.
-    - In case of other primitive types (number, boolean, or string), `first` must be `begin()` and `last` must be
-      `end()`. In this case, the value is copied. Otherwise,
+    - In case of other primitive types (number, boolean, string, or binary), `first` must be `begin()` and `last`
+      must be `end()`. In this case, the value is copied. Otherwise,
      [`invalid_iterator.204`](../../home/exceptions.md#jsonexceptioninvalid_iterator204) is thrown.
    - In case of structured types (array, object), the constructor behaves as similar versions for `std::vector` or
      `std::map`; that is, a JSON array or object is constructed from the values in the range.
@@ -159,6 +178,8 @@ basic_json(basic_json&& other) noexcept;
    - `CompatibleType` is not `basic_json` (to avoid hijacking copy/move constructors),
    - `CompatibleType` is not a different `basic_json` type (i.e. with different template arguments)
    - `CompatibleType` is not a `basic_json` nested type (e.g., `json_pointer`, `iterator`, etc.)
+    - if [`JSON_DISABLE_TUPLE_REFERENCE_CONVERSION`](../macros/json_disable_tuple_reference_conversion.md) is defined
+      to `1`: `CompatibleType` is not a one-element `std::tuple` holding a reference to `basic_json`
    - `json_serializer<U>` (with `U = uncvref_t<CompatibleType>`) has a `to_json(basic_json_t&, CompatibleType&&)`
       method

@@ -169,8 +190,8 @@ basic_json(basic_json&& other) noexcept;
    - `BasicJsonType` has different template arguments than `basic_json_t`.
    
    **Note:** For cross-`basic_json` conversions to produce correct results, the target `basic_json`'s
-    `object_t::key_type` and `string_t` must be directly constructible from the source `basic_json`'s
-    corresponding types. See the description of overload (4) above for details on what happens when
+    [`object_t`](object_t.md)`::key_type` and [`string_t`](string_t.md) must be directly constructible from the source
+    `basic_json`'s corresponding types. See the description of overload (4) above for details on what happens when
    this requirement is not met.

 `U`:
@@ -242,8 +263,8 @@ basic_json(basic_json&& other) noexcept;
      and `last` are not compatible (i.e., do not belong to the same JSON value). In this case, the range
      `[first, last)` is undefined.
    - Throws [`invalid_iterator.204`](../../home/exceptions.md#jsonexceptioninvalid_iterator204) if iterators `first`
-      and `last` belong to a primitive type (number, boolean, or string), but `first` does not point to the first
-      element anymore. In this case, the range `[first, last)` is undefined. See the example code below.
+      and `last` belong to a primitive type (number, boolean, string, or binary), but `first` does not point to the
+      first element anymore. In this case, the range `[first, last)` is undefined. See the example code below.
    - Throws [`invalid_iterator.206`](../../home/exceptions.md#jsonexceptioninvalid_iterator206) if iterators `first`
      and `last` belong to a `#!json null` value. In this case, the range `[first, last)` is undefined.
 8. (none)
@@ -272,6 +293,15 @@ basic_json(basic_json&& other) noexcept;
        When used without parentheses around an empty initializer list, `basic_json()` is called instead of this
        function, yielding the JSON `#!json null` value.

+- Overload 4:
+
+    !!! info "Implicit conversion"
+
+        The conversion is implicit unless [`JSON_USE_IMPLICIT_CONVERSIONS`](../macros/json_use_implicit_conversions.md)
+        is defined to `0` and `BasicJsonType::string_t` differs from `string_t`. In that case, the constructor is
+        `explicit`, so a JSON value with a different string type is no longer silently converted, for example when it is
+        passed to a function taking `#!cpp const json&`. Write `#!cpp json(other)` or `#!cpp other.get<json>()` instead.
+
 - Overload 7:

    !!! info "Preconditions"
@@ -345,6 +375,22 @@ basic_json(basic_json&& other) noexcept;

    Note the output is platform-dependent.

+??? example "Example: (4) create a JSON value from another `basic_json` specialization"
+
+    The example below shows how a `json` value is converted to an `ordered_json` value and back using the converting
+    constructor. Note how the original insertion order of `oj` is not restored, because it was already given up when
+    converting to `json`, whose `object_t` sorts by key.
+
+    ```cpp
+    --8<-- "examples/basic_json__BasicJsonType.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/basic_json__BasicJsonType.output"
+    ```
+
 ??? example "Example: (5) create a container (array or object) from an initializer list"

    The example below shows how JSON values are created from initializer lists.
@@ -415,14 +461,26 @@ basic_json(basic_json&& other) noexcept;
    --8<-- "examples/basic_json__moveconstructor.output"
    ```

+## See also
+
+- [array](array.md) create a JSON array value, forcing array creation from an initializer list even when it looks like
+  an object
+- [object](object.md) create a JSON object value, forcing object creation from an initializer list
+- [binary](binary.md) create a JSON binary array value
+- [operator=](operator=.md) copy assignment operator
+- [Creating JSON values](../../features/creating_values.md) - the article on creating JSON values
+
 ## Version history

 1. Since version 1.0.0.
 2. Since version 1.0.0.
 3. Since version 2.1.0.
-4. Since version 3.2.0.
+4. Since version 3.2.0. Explicit for different string types if `JSON_USE_IMPLICIT_CONVERSIONS` is `0` since
+   version 3.13.0.
 5. Since version 1.0.0.
 6. Since version 1.0.0.
-7. Since version 1.0.0.
+7. Since version 1.0.0. Fixed in version 3.13.0 to also check the iterator range for binary values; before, a range
+   that did not cover the whole value (such as `(end(), end())`) was accepted and the whole binary value was copied,
+   unlike the other primitive types.
 8. Since version 1.0.0.
 9. Since version 1.0.0.
@@ -37,6 +37,14 @@ Constant.
    --8<-- "examples/begin.output"
    ```

+## See also
+
+- [end](end.md) returns an iterator to one past the last element
+- [cbegin](cbegin.md) returns a const iterator to the first element
+- [rbegin](rbegin.md) returns a reverse iterator to the last element
+- [items](items.md) returns an iteration proxy to access keys and values during range-based for loops
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -7,9 +7,9 @@ static basic_json binary(typename binary_t::container_type&& init);

 // (2)
 static basic_json binary(const typename binary_t::container_type& init,
-                         std::uint8_t subtype);
+                         typename binary_t::subtype_type subtype);
 static basic_json binary(typename binary_t::container_type&& init,
-                         std::uint8_t subtype);
+                         typename binary_t::subtype_type subtype);
 ```

 1. Creates a JSON binary array value from a given binary container.
@@ -61,6 +61,15 @@ initialization of a binary array type, for backwards compatibility and so it doe
    --8<-- "examples/binary.output"
    ```

+## See also
+
+- [binary_t](binary_t.md) type for binary values
+- [get_binary](get_binary.md) get a reference to the stored binary value
+- [is_binary](is_binary.md) return whether the value is binary
+- [byte_container_with_subtype](../byte_container_with_subtype/index.md) container for binary values with subtype
+- [Binary Values](../../features/binary_values.md) - the article on binary values
+
 ## Version history

 - Added in version 3.8.0.
+- Changed the type of `subtype` from `std::uint8_t` to `binary_t::subtype_type` (`std::uint64_t`) in version 3.10.0.
@@ -48,16 +48,16 @@ represent a byte array in modern C++.

 ## Notes

-#### Default type
+### Default type

 The default values for `BinaryType` is `#!cpp std::vector<std::uint8_t>`.

-#### Supported byte types
+### Supported byte types

 `#!cpp std::vector<std::uint8_t>`, `#!cpp std::vector<char>`, and `#!cpp std::vector<std::byte>` are supported.
 Regardless of which of them is configured, [`dump`](dump.md) writes the bytes as the numbers 0..255.

-#### Custom BinaryType behavior
+### Custom BinaryType behavior

 When a custom `BinaryType` is configured (other than the default `#!cpp std::vector<std::uint8_t>`), you can assign
 values of that type directly to a `basic_json` instance, and they will automatically be recognized as binary values
@@ -89,12 +89,12 @@ assert(extracted == data);
 This automatic type detection is a convenience feature that only applies to custom (non-default) `BinaryType` configurations.
 The default `nlohmann::json` continues to treat `#!cpp std::vector<std::uint8_t>` as arrays for backward compatibility.

-#### Storage
+### Storage

 Binary Arrays are stored as pointers in a `basic_json` type. That is, for any access to array values, a pointer of the
 type `#!cpp binary_t*` must be dereferenced.

-#### Notes on subtypes
+### Notes on subtypes

 - CBOR
    - Binary values are represented as byte strings. Subtypes are written as tags.
@@ -21,11 +21,11 @@ To store boolean values in C++, a type is defined by the template parameter  `Bo

 ## Notes

-#### Default type
+### Default type

 With the default values for `BooleanType` (`#!cpp bool`), the default value for `boolean_t` is `#!cpp bool`.

-#### Storage
+### Storage

 Boolean values are stored directly inside a `basic_json` type.

@@ -45,6 +45,10 @@ Boolean values are stored directly inside a `basic_json` type.
    --8<-- "examples/boolean_t.output"
    ```

+## See also
+
+- [is_boolean](is_boolean.md) checks whether the JSON value is a boolean
+
 ## Version history

 - Added in version 1.0.0.
@@ -36,6 +36,13 @@ Constant.
    --8<-- "examples/cbegin.output"
    ```

+## See also
+
+- [begin](begin.md) returns an iterator to the first element
+- [cend](cend.md) returns a const iterator to one past the last element
+- [crbegin](crbegin.md) returns a const reverse iterator to the last element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -38,6 +38,12 @@ store
    --8<-- "examples/cbor_tag_handler_t.output"
    ```

+## See also
+
+- [from_cbor](from_cbor.md) deserializes a JSON value from CBOR
+- [input_format_t](input_format_t.md) the enumeration of supported input formats
+- [CBOR](../../features/binary_formats/cbor.md) - the article on the CBOR format
+
 ## Version history

 - Added in version 3.9.0. Added value `store` in 3.10.0.
@@ -36,6 +36,13 @@ Constant.
    --8<-- "examples/cend.output"
    ```

+## See also
+
+- [end](end.md) returns an iterator to one past the last element
+- [cbegin](cbegin.md) returns a const iterator to the first element
+- [crend](crend.md) returns a const reverse iterator to one before the first element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -7,15 +7,15 @@ void clear() noexcept;
 Clears the content of a JSON value and resets it to the default value as if [`basic_json(value_t)`](basic_json.md) would
 have been called with the current value type from [`type()`](type.md):

-| Value type | initial value        |
-|------------|----------------------|
-| null       | `null`               |
-| boolean    | `false`              |
-| string     | `""`                 |
-| number     | `0`                  |
-| binary     | An empty byte vector |
-| object     | `{}`                 |
-| array      | `[]`                 |
+| Value type | initial value                           |
+|------------|-----------------------------------------|
+| null       | `null`                                  |
+| boolean    | `false`                                 |
+| string     | `""`                                    |
+| number     | `0`                                     |
+| binary     | An empty byte vector with no subtype    |
+| object     | `{}`                                    |
+| array      | `[]`                                    |

 Has the same effect as calling

@@ -52,7 +52,13 @@ All iterators, pointers, and references related to this container are invalidate
    --8<-- "examples/clear.output"
    ```

+## See also
+
+- [erase](erase.md) removes elements from a JSON value
+- [empty](empty.md) checks whether the JSON value has no elements
+
 ## Version history

 - Added in version 1.0.0.
 - Added support for binary types in version 3.8.0.
+- Fixed in version 3.13.0 to also clear the subtype of a binary value; before, the subtype was left unchanged.
@@ -58,11 +58,27 @@ Logarithmic in the size of the JSON object.

 - This method always returns `#!cpp false` when executed on a JSON type that is not an object.
 - This method can be executed on any JSON value type.
+- Calling this function with an integer argument (for example, `#!cpp contains(0)`) does not compile: such an argument
+  would otherwise implicitly convert to a null `#!cpp const char*` and, from there, cause undefined behavior when
+  constructing a `#!cpp std::string` for the object key. To check for an array element instead, use [`at`](at.md),
+  [`operator[]`](operator%5B%5D.md), or compare against [`size`](size.md).

 !!! info "Postconditions"

    If `#!cpp j.contains(x)` returns `#!c true` for a key or JSON pointer `x`, then it is safe to call `j[x]`.

+!!! warning "Deprecation"
+
+    Overload (3) also accepts a [`json_pointer`](../json_pointer/index.md) whose template argument is a `basic_json`
+    specialization (e.g., `nlohmann::json_pointer<nlohmann::json>`) instead of a string type. This is deprecated since
+    version 3.11.0 and will be removed in a future major version; use `basic_json::json_pointer` (for `json`,
+    `nlohmann::json_pointer<std::string>`) instead.
+
+    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
+    function.
+
+    See the [migration guide](../../integration/migration_guide.md#json-pointers) for how to update existing code.
+
 ## Examples

 ??? example "Example: (1) check with key"
@@ -115,5 +131,9 @@ Logarithmic in the size of the JSON object.
 ## Version history

 1. Added in version 3.11.0.
-2. Added in version 3.6.0. Extended template `KeyType` to support comparable types in version 3.11.0.
+2. Added in version 3.6.0. Extended template `KeyType` to support comparable types in version 3.11.0. Fixed in
+   version 3.13.0 to consistently accept `std::string_view`-convertible keys, as already supported by
+   [`operator[]`](operator[].md), [`at`](at.md), [`value`](value.md), and other lookup functions.
 3. Added in version 3.7.0.
+4. Deleted overloads for integral key types added in version 3.13.0 to reject such calls at compile time instead of
+   causing undefined behavior at runtime.
@@ -40,7 +40,11 @@ Logarithmic in the size of the JSON object.

 ## Notes

-This method always returns `0` when executed on a JSON type that is not an object.
+- This method always returns `0` when executed on a JSON type that is not an object.
+- Calling this function with an integer argument (for example, `#!cpp count(0)`) does not compile: such an argument
+  would otherwise implicitly convert to a null `#!cpp const char*` and, from there, cause undefined behavior when
+  constructing a `#!cpp std::string` for the object key. To check for an array element instead, use [`at`](at.md),
+  [`operator[]`](operator%5B%5D.md), or compare against [`size`](size.md).

 ## Examples

@@ -80,4 +84,8 @@ This method always returns `0` when executed on a JSON type that is not an objec
 ## Version history

 1. Added in version 3.11.0.
-2. Added in version 1.0.0. Changed parameter `key` type to `KeyType&&` in version 3.11.0.
+2. Added in version 1.0.0. Changed parameter `key` type to `KeyType&&` in version 3.11.0. Fixed in version 3.13.0 to
+   consistently accept `std::string_view`-convertible keys, as already supported by [`operator[]`](operator[].md),
+   [`at`](at.md), [`value`](value.md), and other lookup functions.
+3. Deleted overload for integral key types added in version 3.13.0 to reject such calls at compile time instead of
+   causing undefined behavior at runtime.
@@ -36,6 +36,13 @@ Constant.
    --8<-- "examples/crbegin.output"
    ```

+## See also
+
+- [crend](crend.md) returns a const reverse iterator to one before the first element
+- [rbegin](rbegin.md) returns a reverse iterator to the last element
+- [cbegin](cbegin.md) returns a const iterator to the first element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -37,6 +37,13 @@ Constant.
    --8<-- "examples/crend.output"
    ```

+## See also
+
+- [crbegin](crbegin.md) returns a const reverse iterator to the last element
+- [rend](rend.md) returns a reverse iterator to one before the first element
+- [cend](cend.md) returns a const iterator to one past the last element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -30,6 +30,11 @@ The actual comparator used depends on [`object_t`](object_t.md) and can be obtai
    --8<-- "examples/default_object_comparator_t.output"
    ```

+## See also
+
+- [object_comparator_t](object_comparator_t.md) the comparator actually used by `object_t`
+- [object_t](object_t.md) the type used to store JSON objects
+
 ## Version history

 - Added in version 3.11.0.
@@ -25,10 +25,12 @@ and `ensure_ascii` parameters.
    result consists of ASCII characters only.

 `error_handler` (in)
-:   how to react on decoding errors; there are three possible values (see [`error_handler_t`](error_handler_t.md):
+:   how to react on decoding errors; there are four possible values (see [`error_handler_t`](error_handler_t.md):
    `strict` (throws an exception in case a decoding error occurs; default), `replace` (replace invalid UTF-8 sequences
-    with U+FFFD), and `ignore` (ignore invalid UTF-8 sequences during serialization; all valid bytes are copied to the
-    output unchanged, and invalid bytes are dropped)).
+    with U+FFFD), `ignore` (ignore invalid UTF-8 sequences during serialization; all valid bytes are copied to the
+    output unchanged, and invalid bytes are dropped), and `keep` (write the ill-formed bytes to the output as is,
+    without escaping them, even if `ensure_ascii` is `#!cpp true`; the result is then not valid UTF-8, but equals the
+    input bytes exactly, and well-formed characters around the ill-formed bytes are still escaped as usual)).
    
 ## Return value

@@ -94,3 +96,4 @@ Binary values are serialized as an object containing two keys:
 - Indentation character `indent_char`, option `ensure_ascii` and exceptions added in version 3.0.0.
 - Error handlers added in version 3.4.0.
 - Serialization of binary values added in version 3.8.0.
+- Error handler `keep` added in version 3.13.0.
@@ -31,7 +31,8 @@ a `#!cpp bool` denoting whether the insertion took place.

 ## Exception safety

-Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+Strong guarantee: if an exception is thrown, there are no changes to any JSON value. As an exception, a `#!json null`
+value is converted to an empty object before the element is added and keeps that type if adding the element throws.

 ## Exceptions

@@ -69,3 +70,5 @@ Logarithmic in the size of the container, O(log(`size()`)).
 ## Version history

 - Since version 2.0.8.
+- Fixed in version 3.13.0: for [`ordered_json`](../ordered_json.md), the value could previously only be passed as an
+  rvalue; it can now also be passed as an lvalue or a `#!cpp const` lvalue, matching the behavior of `json`.
@@ -28,6 +28,11 @@ iterator is invalidated.

 reference to the inserted element

+## Exception safety
+
+Strong guarantee: if an exception is thrown, there are no changes to any JSON value. As an exception, a `#!json null`
+value is converted to an empty array before the element is added and keeps that type if adding the element throws.
+
 ## Exceptions

 Throws [`type_error.311`](../../home/exceptions.md#jsonexceptiontype_error311) when called on a type other than JSON
@@ -60,6 +60,11 @@ itself is empty which is `#!cpp false` in the case of a string.
    --8<-- "examples/empty.output"
    ```

+## See also
+
+- [size](size.md) returns the number of elements
+- [clear](clear.md) clears the content and resets the value to the default value
+
 ## Version history

 - Added in version 1.0.0.
@@ -37,6 +37,13 @@ Constant.
    --8<-- "examples/end.output"
    ```

+## See also
+
+- [begin](begin.md) returns an iterator to the first element
+- [cend](cend.md) returns a const iterator to one past the last element
+- [rend](rend.md) returns a reverse iterator to one before the first element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -213,5 +213,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Added in version 1.0.0. Added support for binary types in version 3.8.0.
 2. Added in version 1.0.0. Added support for binary types in version 3.8.0.
 3. Added in version 1.0.0.
-4. Added in version 3.11.0.
+4. Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept `std::string_view`-convertible keys, as
+   already supported by [`operator[]`](operator[].md), [`at`](at.md), [`value`](value.md), and other lookup
+   functions.
 5. Added in version 1.0.0.
@@ -4,15 +4,31 @@
 enum class error_handler_t {
    strict,
    replace,
-    ignore
+    ignore,
+    keep
 };
 ```

-This enumeration is used in the [`dump`](dump.md) function to choose how to treat decoding errors while serializing a
-`basic_json` value. Three values are differentiated:
+This enumeration is used to choose how to treat ill-formed UTF-8 in a string value or object key:
+
+- [`dump`](dump.md) uses it while serializing a `basic_json` value to text.
+- [`to_cbor`](to_cbor.md), [`to_msgpack`](to_msgpack.md), [`to_ubjson`](to_ubjson.md), [`to_bjdata`](to_bjdata.md),
+  and [`to_bson`](to_bson.md) use it while serializing a `basic_json` value to that binary format. Their default is
+  `keep`, as no binary writer checked before this parameter was added. CBOR, UBJSON, BJData, and BSON require valid
+  UTF-8, so for these four the default is `strict` if [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md)
+  is enabled; MessagePack's specification explicitly allows a string to contain ill-formed UTF-8, so `to_msgpack`
+  stays at `keep`. `to_bon8` does not take this parameter: BON8 always validates, since UTF-8 lead bytes are
+  structural to that format.
+- [`from_cbor`](from_cbor.md), [`from_msgpack`](from_msgpack.md), [`from_ubjson`](from_ubjson.md),
+  [`from_bjdata`](from_bjdata.md), and [`from_bson`](from_bson.md) use it while parsing that binary format, to decide
+  whether to check a string value or object key for well-formed UTF-8 at all; by default (`keep`) they do not, as no
+  binary reader did before this parameter was added. `from_bon8` does not take this parameter, for the same reason
+  `to_bon8` does not.
+
+Four values are differentiated:

 strict
-:   throw a `type_error` exception in case of invalid UTF-8
+:   throw a `type_error`/`parse_error` exception in case of invalid UTF-8

 replace
 :   replace invalid UTF-8 sequences with U+FFFD (� REPLACEMENT CHARACTER)
@@ -20,6 +36,12 @@ replace
 ignore
 :   ignore invalid UTF-8 sequences; all valid bytes are copied to the output unchanged, and invalid bytes are dropped

+keep
+:   keep invalid UTF-8 sequences unchanged; only meaningful for the binary formats mentioned above, since [`dump`]
+    (dump.md) itself must produce text, and `keep` there writes the ill-formed bytes to the output as is, so the
+    result is then not valid UTF-8 (but still equals the input bytes exactly, including around any well-formed
+    characters, which are still escaped as usual)
+
 ## Examples

 ??? example
@@ -37,6 +59,13 @@ ignore
    --8<-- "examples/error_handler_t.output"
    ```

+## See also
+
+- [dump](dump.md) serializes a JSON value, with an `error_handler_t` parameter to configure invalid UTF-8 handling
+- [Handling invalid UTF-8](../../features/serialization.md#handling-invalid-utf-8) - the article on handling invalid UTF-8
+
 ## Version history

 - Added in version 3.4.0.
+- Added `keep`, and made this enumeration apply to the binary readers and writers in addition to `dump`, in version
+  3.13.0.
@@ -44,7 +44,11 @@ Logarithmic in the size of the JSON object.

 ## Notes

-This method always returns `end()` when executed on a JSON type that is not an object.
+- This method always returns `end()` when executed on a JSON type that is not an object.
+- Calling this function with an integer argument (for example, `#!cpp find(0)`) does not compile: such an argument
+  would otherwise implicitly convert to a null `#!cpp const char*` and, from there, cause undefined behavior when
+  constructing a `#!cpp std::string` for the object key. To access an array element instead, use [`at`](at.md),
+  [`operator[]`](operator%5B%5D.md), or compare against [`size`](size.md).

 ## Examples

@@ -84,4 +88,8 @@ This method always returns `end()` when executed on a JSON type that is not an o
 ## Version history

 1. Added in version 3.11.0.
-2. Added in version 1.0.0. Changed to support comparable types in version 3.11.0.
+2. Added in version 1.0.0. Changed to support comparable types in version 3.11.0. Fixed in version 3.13.0 to
+   consistently accept `std::string_view`-convertible keys, as already supported by [`operator[]`](operator[].md),
+   [`at`](at.md), [`value`](value.md), and other lookup functions.
+3. Deleted overloads for integral key types added in version 3.13.0 to reject such calls at compile time instead of
+   causing undefined behavior at runtime.
@@ -27,7 +27,7 @@ Empty objects and arrays are flattened to `#!json null` and will not be reconstr

 ## Examples

-??? example
+??? example "Example: flatten a JSON object"

    The following code shows how a JSON object is flattened to an object whose keys consist of JSON pointers.
    
@@ -41,6 +41,21 @@ Empty objects and arrays are flattened to `#!json null` and will not be reconstr
    --8<-- "examples/flatten.output"
    ```

+??? example "Example: empty objects and arrays are flattened to `#!json null`"
+
+    The following code shows that an empty object and an empty array are both flattened to `#!json null`, and that
+    `unflatten()` restores them as `#!json null` rather than as empty containers.
+
+    ```cpp
+    --8<-- "examples/flatten__empty.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/flatten__empty.output"
+    ```
+
 ## See also

 - [unflatten](unflatten.md) the reverse function
@@ -5,12 +5,14 @@
 template<typename InputType>
 static basic_json from_bjdata(InputType&& i,
                              const bool strict = true,
-                              const bool allow_exceptions = true);
+                              const bool allow_exceptions = true,
+                              const error_handler_t error_handler = error_handler_t::keep);
 // (2)
 template<typename IteratorType, typename SentinelType = IteratorType>
 static basic_json from_bjdata(IteratorType first, SentinelType last,
                              const bool strict = true,
-                              const bool allow_exceptions = true);
+                              const bool allow_exceptions = true,
+                              const error_handler_t error_handler = error_handler_t::keep);
 ```

 Deserializes a given input to a JSON value using the BJData (Binary JData) serialization format.
@@ -58,6 +60,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `allow_exceptions` (in)
 :   whether to throw exceptions in case of a parse error (optional, `#!cpp true` by default)

+`error_handler` (in)
+:   how to treat a string value or object key that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    BJData does not require a decoder to reject ill-formed UTF-8, so checking is opt-in: the default, `keep`, does not
+    check at all, as every binary reader did before this parameter was added; `strict` checks and throws;
+    `replace`/`ignore` sanitize the string the same way [`dump`](dump.md) would
+
 ## Return value

 deserialized JSON value; in case of a parse error and `allow_exceptions` set to `#!cpp false`, the return value will be
@@ -73,7 +81,7 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
  the end of the file was not reached when `strict` was set to true
 - Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if a parse error occurs
 - Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a string could not be parsed
-  successfully
+  successfully, or if a string value or object key is not valid UTF-8 and `error_handler` is `strict`
 - Throws [out_of_range.408](../../home/exceptions.md#jsonexceptionout_of_range408) if the size of an optimized container
  or n-dimensional array cannot be represented by `std::size_t`

@@ -111,3 +119,4 @@ Linear in the size of the input.
 - Added in version 3.11.0.
 - Extended container support (1) to include types with lvalue-only ADL `begin`/`end` (matching `std::begin`/`std::end` semantics) in version 3.13.0.
 - Extended overload (2) to accept heterogeneous iterator+sentinel pairs (C++20 ranges support) in version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0.
@@ -5,12 +5,14 @@
 template<typename InputType>
 static basic_json from_bson(InputType&& i,
                            const bool strict = true,
-                            const bool allow_exceptions = true);
+                            const bool allow_exceptions = true,
+                            const error_handler_t error_handler = error_handler_t::keep);
 // (2)
 template<typename IteratorType, typename SentinelType = IteratorType>
 static basic_json from_bson(IteratorType first, SentinelType last,
                            const bool strict = true,
-                            const bool allow_exceptions = true);
+                            const bool allow_exceptions = true,
+                            const error_handler_t error_handler = error_handler_t::keep);
 ```

 Deserializes a given input to a JSON value using the BSON (Binary JSON) serialization format.
@@ -58,6 +60,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `allow_exceptions` (in)
 :   whether to throw exceptions in case of a parse error (optional, `#!cpp true` by default)

+`error_handler` (in)
+:   how to treat a string value or object key that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    BSON does not require a decoder to reject ill-formed UTF-8, so checking is opt-in: the default, `keep`, does not
+    check at all, as every binary reader did before this parameter was added; `strict` checks and throws;
+    `replace`/`ignore` sanitize the string the same way [`dump`](dump.md) would
+
 ## Return value

 deserialized JSON value; in case of a parse error and `allow_exceptions` set to `#!cpp false`, the return value will be
@@ -75,6 +83,8 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
  invalid string or byte array length)
 - Throws [`parse_error.114`](../../home/exceptions.md#jsonexceptionparse_error114) if an unsupported BSON record type is
  encountered
+- Throws [`parse_error.113`](../../home/exceptions.md#jsonexceptionparse_error113) if a string value or object key is
+  not valid UTF-8 and `error_handler` is `strict`

 ## Complexity

@@ -111,6 +121,7 @@ Linear in the size of the input.
 - Added in version 3.4.0.
 - Extended container support (1) to include types with lvalue-only ADL `begin`/`end` (matching `std::begin`/`std::end` semantics) in version 3.13.0.
 - Extended overload (2) to accept heterogeneous iterator+sentinel pairs (C++20 ranges support) in version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0.

 !!! warning "Deprecation"

@@ -123,3 +134,5 @@ Linear in the size of the input.

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -6,14 +6,16 @@ template<typename InputType>
 static basic_json from_cbor(InputType&& i,
                            const bool strict = true,
                            const bool allow_exceptions = true,
-                            const cbor_tag_handler_t tag_handler = cbor_tag_handler_t::error);
+                            const cbor_tag_handler_t tag_handler = cbor_tag_handler_t::error,
+                            const error_handler_t error_handler = error_handler_t::keep);

 // (2)
 template<typename IteratorType, typename SentinelType = IteratorType>
 static basic_json from_cbor(IteratorType first, SentinelType last,
                            const bool strict = true,
                            const bool allow_exceptions = true,
-                            const cbor_tag_handler_t tag_handler = cbor_tag_handler_t::error);
+                            const cbor_tag_handler_t tag_handler = cbor_tag_handler_t::error,
+                            const error_handler_t error_handler = error_handler_t::keep);
 ```

 Deserializes a given input to a JSON value using the CBOR (Concise Binary Object Representation) serialization format.
@@ -65,6 +67,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 :   how to treat CBOR tags (optional, `error` by default); see [`cbor_tag_handler_t`](cbor_tag_handler_t.md) for more
    information

+`error_handler` (in)
+:   how to treat a string value or object key that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    CBOR does not require a decoder to reject ill-formed UTF-8, so checking is opt-in: the default, `keep`, does not
+    check at all, as every binary reader did before this parameter was added; `strict` checks and throws;
+    `replace`/`ignore` sanitize the string the same way [`dump`](dump.md) would
+
 ## Return value

 deserialized JSON value; in case of a parse error and `allow_exceptions` set to `#!cpp false`, the return value will be
@@ -80,8 +88,9 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
  the end of the file was not reached when `strict` was set to true
 - Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if unsupported features from CBOR were
  used in the given input or if the input is not valid CBOR
- Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a map key is not a string (keys of other
-  types are not supported, as JSON object keys are always strings) or a string is malformed
+- Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a map key is not a string (keys of
+  other types are not supported, as JSON object keys are always strings), or if a string value or object key is not
+  valid UTF-8 and `error_handler` is `strict`

 ## Complexity

@@ -121,6 +130,7 @@ Linear in the size of the input.
 - Added `tag_handler` parameter in version 3.9.0.
 - Extended container support (1) to include types with lvalue-only ADL `begin`/`end` (matching `std::begin`/`std::end` semantics) in version 3.13.0.
 - Extended overload (2) to accept heterogeneous iterator+sentinel pairs (C++20 ranges support) in version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0.

 !!! warning "Deprecation"

@@ -133,3 +143,5 @@ Linear in the size of the input.

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -5,12 +5,14 @@
 template<typename InputType>
 static basic_json from_msgpack(InputType&& i,
                               const bool strict = true,
-                               const bool allow_exceptions = true);
+                               const bool allow_exceptions = true,
+                               const error_handler_t error_handler = error_handler_t::keep);
 // (2)
 template<typename IteratorType, typename SentinelType = IteratorType>
 static basic_json from_msgpack(IteratorType first, SentinelType last,
                               const bool strict = true,
-                               const bool allow_exceptions = true);
+                               const bool allow_exceptions = true,
+                               const error_handler_t error_handler = error_handler_t::keep);
 ```

 Deserializes a given input to a JSON value using the MessagePack serialization format.
@@ -58,6 +60,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `allow_exceptions` (in)
 :   whether to throw exceptions in case of a parse error (optional, `#!cpp true` by default)

+`error_handler` (in)
+:   how to treat a string value or object key that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    MessagePack's specification explicitly allows ill-formed UTF-8, so checking is opt-in: the default, `keep`, does
+    not check at all, as every binary reader did before this parameter was added; `strict` checks and throws;
+    `replace`/`ignore` sanitize the string the same way [`dump`](dump.md) would
+
 ## Return value

 deserialized JSON value; in case of a parse error and `allow_exceptions` set to `#!cpp false`, the return value will be
@@ -73,8 +81,9 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
  the end of the file was not reached when `strict` was set to true
 - Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if unsupported features from
  MessagePack were used in the given input or if the input is not valid MessagePack
- Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a map key is not a string (keys of other
-  types are not supported, as JSON object keys are always strings) or a string is malformed
+- Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a map key is not a string (keys of
+  other types are not supported, as JSON object keys are always strings), or if a string value or object key is not
+  valid UTF-8 and `error_handler` is `strict`

 ## Complexity

@@ -113,6 +122,7 @@ Linear in the size of the input.
 - Added `allow_exceptions` parameter in version 3.2.0.
 - Extended container support (1) to include types with lvalue-only ADL `begin`/`end` (matching `std::begin`/`std::end` semantics) in version 3.13.0.
 - Extended overload (2) to accept heterogeneous iterator+sentinel pairs (C++20 ranges support) in version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0.

 !!! warning "Deprecation"

@@ -125,3 +135,5 @@ Linear in the size of the input.

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -5,12 +5,14 @@
 template<typename InputType>
 static basic_json from_ubjson(InputType&& i,
                              const bool strict = true,
-                              const bool allow_exceptions = true);
+                              const bool allow_exceptions = true,
+                              const error_handler_t error_handler = error_handler_t::keep);
 // (2)
 template<typename IteratorType, typename SentinelType = IteratorType>
 static basic_json from_ubjson(IteratorType first, SentinelType last,
                              const bool strict = true,
-                              const bool allow_exceptions = true);
+                              const bool allow_exceptions = true,
+                              const error_handler_t error_handler = error_handler_t::keep);
 ```

 Deserializes a given input to a JSON value using the UBJSON (Universal Binary JSON) serialization format.
@@ -58,6 +60,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `allow_exceptions` (in)
 :   whether to throw exceptions in case of a parse error (optional, `#!cpp true` by default)

+`error_handler` (in)
+:   how to treat a string value or object key that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    UBJSON does not require a decoder to reject ill-formed UTF-8, so checking is opt-in: the default, `keep`, does not
+    check at all, as every binary reader did before this parameter was added; `strict` checks and throws;
+    `replace`/`ignore` sanitize the string the same way [`dump`](dump.md) would
+
 ## Return value

 deserialized JSON value; in case of a parse error and `allow_exceptions` set to `#!cpp false`, the return value will be
@@ -73,7 +81,7 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
  the end of the file was not reached when `strict` was set to true
 - Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if a parse error occurs
 - Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a string could not be parsed
-  successfully
+  successfully, or if a string value or object key is not valid UTF-8 and `error_handler` is `strict`
 - Throws [out_of_range.408](../../home/exceptions.md#jsonexceptionout_of_range408) if the size of an optimized container
  or n-dimensional array cannot be represented by `std::size_t`

@@ -112,6 +120,7 @@ Linear in the size of the input.
 - Added `allow_exceptions` parameter in version 3.2.0.
 - Extended container support (1) to include types with lvalue-only ADL `begin`/`end` (matching `std::begin`/`std::end` semantics) in version 3.13.0.
 - Extended overload (2) to accept heterogeneous iterator+sentinel pairs (C++20 ranges support) in version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0.

 !!! warning "Deprecation"

@@ -124,3 +133,5 @@ Linear in the size of the input.

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -13,16 +13,16 @@ BasicJsonType get() const;

 // (3)
 template<typename PointerType>
-PointerType get_ptr();
+PointerType get() noexcept;

 template<typename PointerType>
-constexpr const PointerType get_ptr() const noexcept;
+const PointerType get() const noexcept;  // constexpr since C++14
 ```

 1. Explicit type conversion between the JSON value and a compatible value which is
   [CopyConstructible](https://en.cppreference.com/w/cpp/named_req/CopyConstructible) and
   [DefaultConstructible](https://en.cppreference.com/w/cpp/named_req/DefaultConstructible). The value is converted by
-   calling the `json_serializer<ValueType>` `from_json()` method.
+   calling the [`json_serializer<ValueType>`](json_serializer.md) `from_json()` method.
   
    The function is equivalent to executing
    ```cpp
@@ -84,6 +84,12 @@ constexpr const PointerType get_ptr() const noexcept;
 3. pointer to the internally stored JSON value if the requested pointer type fits to the JSON value; `#!cpp nullptr`
   otherwise

+## Exception safety
+
+Depends on what `json_serializer<ValueType>` `from_json()` method throws for overloads (1) and (2); the JSON value
+itself is never modified, since `get()` is a `#!cpp const` member function. No-throw guarantee for overload (3): this
+function never throws exceptions.
+
 ## Exceptions

 Depends on what `json_serializer<ValueType>` `from_json()` method throws
@@ -123,13 +129,13 @@ overload (3).

 ## Examples

-??? example
+??? example "Example: (1) explicit conversion to compatible types"

    The example below shows several conversions from JSON values
    to other types. There a few things to note: (1) Floating-point numbers can
    be converted to integers, (2) A JSON array can be converted to a standard
    `std::vector<short>`, (3) A JSON object can be converted to C++
-    associative containers such as `std::unordered_map<std::string, json>`.
+    associative containers such as `std::map<std::string, json>`.
        
    ```cpp
    --8<-- "examples/get__ValueType_const.cpp"
@@ -141,7 +147,21 @@ overload (3).
    --8<-- "examples/get__ValueType_const.output"
    ```

-??? example
+??? example "Example: (2) explicit conversion to another `basic_json` specialization"
+
+    The example below shows how a `json` value is converted to an `ordered_json` value using `get<BasicJsonType>()`.
+
+    ```cpp
+    --8<-- "examples/get__BasicJsonType.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/get__BasicJsonType.output"
+    ```
+
+??? example "Example: (3) explicit pointer access to the stored value"

    The example below shows how pointers to internal values of a JSON value can be requested. Note that no type
    conversions are made and a `#cpp nullptr` is returned if the value and the requested pointer type does not match.
@@ -10,6 +10,14 @@ Returns the allocator associated with the container.

 associated allocator

+## Exception safety
+
+Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+
+## Complexity
+
+Constant.
+
 ## Examples

 ??? example
@@ -26,6 +34,11 @@ associated allocator
    --8<-- "examples/get_allocator.output"
    ```

+## See also
+
+- [basic_json](index.md#template-parameters) the class template, with `AllocatorType` as one of its template parameters
+- [Template Parameter Requirements](../../features/types/template_parameters.md#allocatortype) - the requirements for `AllocatorType`
+
 ## Version history

 - Added in version 1.0.0.
@@ -8,7 +8,7 @@ ValueType& get_to(ValueType& v) const noexcept(
 ```

 Explicit type conversion between the JSON value and a compatible value. The value is filled into the input parameter by
-calling the `json_serializer<ValueType>` `from_json()` method.
+calling the [`json_serializer<ValueType>`](json_serializer.md) `from_json()` method.

 The function is equivalent to executing
 ```cpp
@@ -34,6 +34,11 @@ the compiler reports that no matching `get_to` was found.

 the input parameter, allowing chaining calls

+## Exception safety
+
+Depends on what `json_serializer<ValueType>` `from_json()` method throws; the JSON value itself is never modified,
+since `get_to()` is a `#!cpp const` member function.
+
 ## Exceptions

 Depends on what `json_serializer<ValueType>` `from_json()` method throws
@@ -49,7 +54,7 @@ Depends on the `json_serializer<ValueType>::from_json()` implementation.
    The example below shows several conversions from JSON values to other types. There a few things to note: (1)
    Floating-point numbers can be converted to integers, (2) A JSON array can be converted to a standard
    `#!cpp std::vector<short>`, (3) A JSON object can be converted to C++ associative containers such as
-    `#cpp std::unordered_map<std::string, json>`.
+    `#!cpp std::map<std::string, json>`.
        
    ```cpp
    --8<-- "examples/get_to.cpp"
@@ -200,6 +200,7 @@ Direct access to the stored value of a JSON value.
 - [**get_ref**](get_ref.md) - get a reference value
 - [**operator ValueType**](operator_ValueType.md) - get a value
 - [**get_binary**](get_binary.md) - get a binary value
+- [**as_base_class**](as_base_class.md) - access the custom base class

 ### Element access

@@ -51,6 +51,11 @@ bon8
    --8<-- "examples/sax_parse__binary.output"
    ```

+## See also
+
+- [sax_parse](sax_parse.md) generic SAX parse interface, taking an `input_format_t` to select the input format
+- [cbor_tag_handler_t](cbor_tag_handler_t.md) configures how CBOR tags are treated while parsing
+
 ## Version history

 - Added in version 3.2.0.
@@ -109,11 +109,11 @@ Strong exception safety: if an exception occurs, the original value stays intact
 2. Linear in `cnt` plus linear in the distance between `pos` and end of the container.
 3. Linear in `#!cpp std::distance(first, last)` plus linear in the distance between `pos` and end of the container.
 4. Linear in `ilist.size()` plus linear in the distance between `pos` and end of the container.
-5. Logarithmic: `O(N*log(size() + N))`, where `N` is the number of elements to insert.
+5. `O(N*log(size() + N))`, where `N` is the number of elements to insert.

 ## Examples

-??? example "Example (1): insert element into array"
+??? example "Example: (1) insert element into array"

    The example shows how `insert()` is used.
    
@@ -127,7 +127,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
    --8<-- "examples/insert.output"
    ```

-??? example "Example (2): insert copies of element into array"
+??? example "Example: (2) insert copies of element into array"

    The example shows how `insert()` is used.
    
@@ -141,7 +141,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
    --8<-- "examples/insert__count.output"
    ```

-??? example "Example (3): insert a range of elements into an array"
+??? example "Example: (3) insert a range of elements into an array"

    The example shows how `insert()` is used.
    
@@ -155,7 +155,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
    --8<-- "examples/insert__range.output"
    ```

-??? example "Example (4): insert elements from an initializer list into an array"
+??? example "Example: (4) insert elements from an initializer list into an array"

    The example shows how `insert()` is used.
    
@@ -169,7 +169,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
    --8<-- "examples/insert__ilist.output"
    ```

-??? example "Example (5): insert a range of elements into an object"
+??? example "Example: (5) insert a range of elements into an object"

    The example shows how `insert()` is used.
    
@@ -195,5 +195,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Added in version 1.0.0.
 2. Added in version 1.0.0.
 3. Added in version 1.0.0.
-4. Added in version 1.0.0.
+4. Added in version 1.0.0. Fixed in version 3.13.0 to copy the values before inserting; before, an `ilist` that
+   referred to elements of the array being inserted into could insert wrong values, because the range insert could
+   move from or shift an element before it was copied.
 5. Added in version 3.0.0.
@@ -34,6 +34,13 @@ Constant.
    --8<-- "examples/is_array.output"
    ```

+## See also
+
+- [is_object](is_object.md) checks whether the JSON value is an object
+- [is_structured](is_structured.md) checks whether the JSON value is structured (array or object)
+- [type](type.md) returns the type of the JSON value
+- [array_t](array_t.md) the type used to store JSON arrays
+
 ## Version history

 - Added in version 1.0.0.
@@ -34,6 +34,12 @@ Constant.
    --8<-- "examples/is_binary.output"
    ```

+## See also
+
+- [is_primitive](is_primitive.md) checks whether the JSON value is primitive
+- [binary_t](binary_t.md) the type used to store binary values
+- [get_binary](get_binary.md) returns a reference to the stored binary value
+
 ## Version history

 - Added in version 3.8.0.
@@ -34,6 +34,11 @@ Constant.
    --8<-- "examples/is_boolean.output"
    ```

+## See also
+
+- [boolean_t](boolean_t.md) the type used to store JSON booleans
+- [is_primitive](is_primitive.md) checks whether the JSON value is primitive
+
 ## Version history

 - Added in version 1.0.0.
@@ -55,7 +55,7 @@ with `allow_exceptions` set to `#!cpp false`: a parse error then yields a discar

 ## Examples

-??? example
+??? example "Example: `is_discarded()` for ordinary JSON values"

    The following code exemplifies `is_discarded()` for all JSON types.
    
@@ -69,6 +69,22 @@ with `allow_exceptions` set to `#!cpp false`: a parse error then yields a discar
    --8<-- "examples/is_discarded.output"
    ```

+??? example "Example: discarded values from parsing"
+
+    The following code shows the two situations in which a discarded value can be observed: parsing invalid JSON with
+    `allow_exceptions` set to `#!cpp false`, and a parser callback that discards the top-level value (which is replaced
+    by `#!json null` and therefore does *not* remain discarded).
+
+    ```cpp
+    --8<-- "examples/is_discarded__parse.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/is_discarded__parse.output"
+    ```
+
 ## Version history

 - Added in version 1.0.0.
@@ -34,6 +34,13 @@ Constant.
    --8<-- "examples/is_null.output"
    ```

+## See also
+
+- [is_array](is_array.md) checks whether the JSON value is an array
+- [is_object](is_object.md) checks whether the JSON value is an object
+- [type](type.md) returns the type of the JSON value
+- [value_t](value_t.md) the enumeration of JSON types
+
 ## Version history

 - Added in version 1.0.0.
@@ -34,6 +34,13 @@ Constant.
    --8<-- "examples/is_object.output"
    ```

+## See also
+
+- [is_array](is_array.md) checks whether the JSON value is an array
+- [is_structured](is_structured.md) checks whether the JSON value is structured (array or object)
+- [type](type.md) returns the type of the JSON value
+- [object_t](object_t.md) the type used to store JSON objects
+
 ## Version history

 - Added in version 1.0.0.
@@ -34,6 +34,12 @@ Constant.
    --8<-- "examples/is_string.output"
    ```

+## See also
+
+- [is_primitive](is_primitive.md) checks whether the JSON value is primitive
+- [type](type.md) returns the type of the JSON value
+- [string_t](string_t.md) the type used to store JSON strings
+
 ## Version history

 - Added in version 1.0.0.
@@ -114,3 +114,5 @@ When iterating over an array, `key()` will return the index of the element as st

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#miscellaneous-functions) for how to update existing code.
@@ -14,12 +14,12 @@ Examples of such functionality might be metadata, additional member functions (e

 ## Notes

-#### Default type
+### Default type

 The default value for `CustomBaseClass` is `void`. In this case, an
 [empty base class](https://en.cppreference.com/w/cpp/language/ebo) is used and no additional functionality is injected.

-#### Limitations
+### Limitations

 The type `CustomBaseClass` has to be a default-constructible, non-`final` class.
 `basic_json` only supports copy/move construction/assignment if `CustomBaseClass` does so as well.
@@ -27,6 +27,18 @@ A `CustomBaseClass` with non-static data members forfeits `basic_json`'s
 [standard layout](https://en.cppreference.com/w/cpp/named_req/StandardLayoutType) guarantee. See
 [Template Parameter Requirements](../../features/types/template_parameters.md#custombaseclass).

+#### Name conflicts
+
+Since `basic_json` derives from `CustomBaseClass`, members of `basic_json` hide members of `CustomBaseClass` with the
+same name. Hidden members remain accessible via [`as_base_class`](as_base_class.md) or by casting the value to
+`json_base_class_t`.
+
+!!! warning "Avoid generic member names"
+
+    Future versions of the library may add members to `basic_json` that hide members of `CustomBaseClass` that are
+    accessible today. To reduce the risk of such conflicts, avoid generic names for the members of `CustomBaseClass`,
+    for instance by using a distinctive prefix.
+
 ## Examples

 ??? example
@@ -43,6 +55,12 @@ A `CustomBaseClass` with non-static data members forfeits `basic_json`'s
    --8<-- "examples/json_base_class_t.output"
    ```

+## See also
+
+- [as_base_class](as_base_class.md) - access the custom base class
+- [Template Parameter Requirements](../../features/types/template_parameters.md#custombaseclass) - the requirements for `CustomBaseClass`
+
 ## Version history

 - Added in version 3.12.0.
+- Made a public member type in version 3.13.0; it was private before, so it could not be named outside the class.
@@ -15,11 +15,11 @@ using json_serializer = JSONSerializer<T, SFINAE>;

 ## Notes

-#### Default type
+### Default type

 The default values for `json_serializer` is [`adl_serializer`](../adl_serializer/index.md).

-#### Requirements
+### Requirements

 A custom serializer must provide `#!cpp static void to_json(basic_json&, T)` for every type it serializes, and either
 `#!cpp static void from_json(const basic_json&, T&)` or `#!cpp static T from_json(const basic_json&)` for every type it
@@ -42,6 +42,13 @@ deserializes. See [Template Parameter Requirements](../../features/types/templat
    --8<-- "examples/from_json__non_default_constructible.output"
    ```

+## See also
+
+- [adl_serializer](../adl_serializer/index.md) the default `json_serializer`
+- [get](get.md) explicit type conversion using the `json_serializer`'s `from_json()` method
+- [get_to](get_to.md) explicit type conversion into a variable using the `json_serializer`'s `from_json()` method
+- [Arbitrary Type Conversions](../../features/arbitrary_types.md) - the article on converting between JSON values and arbitrary types
+
 ## Version history

 - Since version 2.0.0.
@@ -54,6 +54,12 @@ string elements the JSON value can store which is `1`.

    Note the output is platform-dependent.

+## See also
+
+- [size](size.md) returns the number of elements
+- [array_t](array_t.md) the type used to store JSON arrays
+- [object_t](object_t.md) the type used to store JSON objects
+
 ## Version history

 - Added in version 1.0.0.
@@ -33,10 +33,20 @@ Thereby, `Target` is the current object; that is, the patch is applied to the cu
 `apply_patch` (in)
 :   the patch to apply

+## Exception safety
+
+Basic guarantee: if an exception is thrown during the operation, the JSON value may be partially modified.
+
 ## Complexity

 Linear in the lengths of `apply_patch`.

+## Notes
+
+`apply_patch` may be `#!cpp *this` itself or refer to a value contained in `#!cpp *this` (for example, a subobject
+returned by `#!cpp (*this)[key]`); it is read as it was when `merge_patch()` was called, before any modification of
+`#!cpp *this`.
+
 ## Examples

 ??? example
@@ -61,3 +71,5 @@ Linear in the lengths of `apply_patch`.
 ## Version history

 - Added in version 3.0.0.
+- Fixed use of freed or relocated memory when `apply_patch` is `#!cpp *this` or refers to a value contained in
+  `#!cpp *this`, in version 3.13.0.
@@ -13,7 +13,7 @@ JSON object holding version information

 | key         | description                                                                                                                                                                                                                                                                    |
 |-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `compiler`  | Information on the used compiler. It is an object with the following keys: `c++` (the used C++ standard), `family` (the compiler family; possible values are `clang`, `icc`, `gcc`, `ilecpp`, `msvc`, `pgcpp`, `sunpro`, and `unknown`), and `version` (the compiler version). On HP aCC compilers, `compiler` is instead the plain string `hp`. |
+| `compiler`  | Information on the used compiler. It is an object with the following keys: `c++` (the used C++ standard), `family` (the compiler family; possible values are `clang`, `icc`, `gcc`, `hp`, `ilecpp`, `msvc`, `pgcpp`, `sunpro`, and `unknown`), and `version` (the compiler version). |
 | `copyright` | The copyright line for the library as string.                                                                                                                                                                                                                                  |
 | `name`      | The name of the library as string.                                                                                                                                                                                                                                             |
 | `platform`  | The used platform as string. Possible values are `win32`, `linux`, `apple`, `unix`, and `unknown`.                                                                                                                                                                             |
@@ -32,18 +32,18 @@ type to use.

 ## Notes

-#### Default type
+### Default type

 With the default values for `NumberFloatType` (`double`), the default value for `number_float_t` is `#!cpp double`.

-#### Default behavior
+### Default behavior

 - The restrictions about leading zeros are not enforced in C++. Instead, leading zeros in floating-point literals will
  be ignored. Internally, the value will be stored as a decimal number. For instance, the C++ floating-point literal
  `01.2` will be serialized to `1.2`. During deserialization, leading zeros yield an error.
 - Not-a-number (NaN) values will be serialized to `null`.

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) states:
 > This specification allows implementations to set limits on the range and precision of numbers accepted. Since software
@@ -55,7 +55,7 @@ This implementation does exactly follow this approach, as it uses double precisi
 smaller than `-1.79769313486232e+308` and values greater than `1.79769313486232e+308` will be stored as NaN internally
 and be serialized to `null`.

-#### Storage
+### Storage

 Floating-point number values are stored directly inside a `basic_json` type.

@@ -75,6 +75,13 @@ Floating-point number values are stored directly inside a `basic_json` type.
    --8<-- "examples/number_float_t.output"
    ```

+## See also
+
+- [number_integer_t](number_integer_t.md) the type used to store JSON integer numbers
+- [number_unsigned_t](number_unsigned_t.md) the type used to store JSON unsigned integer numbers
+- [is_number_float](is_number_float.md) checks whether the JSON value is a floating-point number
+- [Number Handling](../../features/types/number_handling.md) - the article on number handling
+
 ## Version history

 - Added in version 1.0.0.
@@ -29,18 +29,18 @@ to use.

 ## Notes

-#### Default type
+### Default type

 With the default values for `NumberIntegerType` (`std::int64_t`), the default value for `number_integer_t` is
 `#!cpp std::int64_t`.

-#### Default behavior
+### Default behavior

 - The restrictions about leading zeros are not enforced in C++. Instead, leading zeros in integer literals lead to an
  interpretation as an octal number. Internally, the value will be stored as a decimal number. For instance, the C++
  integer literal `010` will be serialized to `8`. During deserialization, leading zeros yield an error.

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the range and precision of numbers.
@@ -51,13 +51,13 @@ range will yield over/underflow when used in a constructor. During deserializati
 will automatically be stored as [`number_unsigned_t`](number_unsigned_t.md) or [`number_float_t`](number_float_t.md).

 [RFC 8259](https://tools.ietf.org/html/rfc8259) further states:
-> Note that when such software is used, numbers that are integers and are in the range $[-2^{53}+1, 2^{53}-1]$ are
+> Note that when such software is used, numbers that are integers and are in the range [-2<sup>53</sup>+1, 2<sup>53</sup>-1] are
 > interoperable in the sense that implementations will agree exactly on their numeric values.

 As this range is a subrange of the exactly supported range [INT64_MIN, INT64_MAX], this class's integer type is
 interoperable.

-#### Storage
+### Storage

 Integer number values are stored directly inside a `basic_json` type.

@@ -77,6 +77,13 @@ Integer number values are stored directly inside a `basic_json` type.
    --8<-- "examples/number_integer_t.output"
    ```

+## See also
+
+- [number_unsigned_t](number_unsigned_t.md) the type used to store JSON unsigned integer numbers
+- [number_float_t](number_float_t.md) the type used to store JSON floating-point numbers
+- [is_number_integer](is_number_integer.md) checks whether the JSON value is a signed integer number
+- [Number Handling](../../features/types/number_handling.md) - the article on number handling
+
 ## Version history

 - Added in version 1.0.0.
@@ -30,18 +30,18 @@ the type to use.

 ## Notes

-#### Default type
+### Default type

 With the default values for `NumberUnsignedType` (`std::uint64_t`), the default value for `number_unsigned_t` is
 `#!cpp std::uint64_t`.

-#### Default behavior
+### Default behavior

 - The restrictions about leading zeros are not enforced in C++. Instead, leading zeros in integer literals lead to an
  interpretation as an octal number. Internally, the value will be stored as a decimal number. For instance, the C++
  integer  literal `010` will be serialized to `8`. During deserialization, leading zeros yield an error.

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the range and precision of numbers.
@@ -52,13 +52,13 @@ when used in a constructor. During deserialization, too large or small integer n
 as [`number_integer_t`](number_integer_t.md) or [`number_float_t`](number_float_t.md).

 [RFC 8259](https://tools.ietf.org/html/rfc8259) further states:
-> Note that when such software is used, numbers that are integers and are in the range $[-2^{53}+1, 2^{53}-1]$ are
+> Note that when such software is used, numbers that are integers and are in the range [-2<sup>53</sup>+1, 2<sup>53</sup>-1] are
 > interoperable in the sense that implementations will agree exactly on their numeric values.

 As this range is a subrange (when considered in conjunction with the `number_integer_t` type) of the exactly supported
 range [0, UINT64_MAX], this class's integer type is interoperable.

-#### Storage
+### Storage

 Integer number values are stored directly inside a `basic_json` type.

@@ -78,6 +78,13 @@ Integer number values are stored directly inside a `basic_json` type.
    --8<-- "examples/number_unsigned_t.output"
    ```

+## See also
+
+- [number_integer_t](number_integer_t.md) the type used to store JSON integer numbers
+- [number_float_t](number_float_t.md) the type used to store JSON floating-point numbers
+- [is_number_unsigned](is_number_unsigned.md) checks whether the JSON value is an unsigned integer number
+- [Number Handling](../../features/types/number_handling.md) - the article on number handling
+
 ## Version history

 - Added in version 2.0.0.
@@ -25,6 +25,11 @@ and [`default_object_comparator_t`](default_object_comparator_t.md) otherwise.
    --8<-- "examples/object_comparator_t.output"
    ```

+## See also
+
+- [object_t](object_t.md) the type used to store JSON objects
+- [default_object_comparator_t](default_object_comparator_t.md) the fallback comparator used when `object_t` has no `key_compare` member type
+
 ## Version history

 - Added in version 3.0.0.
@@ -33,7 +33,7 @@ To store objects in C++, a type is defined by the template parameters described

 ## Notes

-#### Default type
+### Default type

 With the default values for `ObjectType` (`std::map`), `StringType` (`std::string`), and `AllocatorType`
 (`std::allocator`), the default value for `object_t` is:
@@ -58,7 +58,7 @@ std::map<

 See [`default_object_comparator_t`](default_object_comparator_t.md) for more information.

-#### Behavior
+### Behavior

 The choice of `object_t` influences the behavior of the JSON class. With the default type, objects have the following
 behavior:
@@ -76,7 +76,7 @@ behavior:
  that they will not be affected by these differences. For instance, `#!json {"b": 1, "a": 2}` and
  `#!json {"a": 2, "b": 1}` will be treated as equal.

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the maximum depth of nesting.
@@ -85,12 +85,12 @@ In this class, the object's limit of nesting is not explicitly constrained. Howe
 introduced by the compiler or runtime environment. A theoretical limit can be queried by calling the
 [`max_size`](max_size.md) function of a JSON object.

-#### Storage
+### Storage

 Objects are stored as pointers in a `basic_json` type. That is, for any access to object values, a pointer of type
 `object_t*` must be dereferenced.

-#### Object key order
+### Object key order

 The order name/value pairs are added to the object are *not* preserved by the library. Therefore, iterating an object
 may return name/value pairs in a different order than they were originally stored. In fact, keys will be traversed in
@@ -98,10 +98,10 @@ alphabetical order as `std::map` with `std::less` is used by default. Please not
 [RFC 8259](https://tools.ietf.org/html/rfc8259), because any order implements the specified "unordered" nature of JSON
 objects.

-#### Cross-`basic_json` conversion requirements
+### Cross-`basic_json` conversion requirements

 When converting an object from one `basic_json` specialization to another via the
-[converting constructor](basic_json.md#overload-4), the target `object_t`'s `key_type` must be
+[converting constructor](basic_json.md) (overload 4), the target `object_t`'s `key_type` must be
 directly constructible from the source `basic_json`'s `string_t` type (or more generally, from the
 source object's key type). If this requirement is not met, the conversion does not fail; instead,
 the object is silently converted as an array of key-value pairs, which is incorrect. See
@@ -123,6 +123,13 @@ the object is silently converted as an array of key-value pairs, which is incorr
    --8<-- "examples/object_t.output"
    ```

+## See also
+
+- [array_t](array_t.md) the type used to store JSON arrays
+- [string_t](string_t.md) the type used to store JSON strings
+- [object_comparator_t](object_comparator_t.md) the comparator used to order object keys
+- [Object Order](../../features/object_order.md) - the article on object key ordering
+
 ## Version history

 - Added in version 1.0.0.
@@ -48,6 +48,12 @@ invalidates all iterators and all references.

 `#!cpp *this`

+## Exception safety
+
+Strong guarantee: if an exception is thrown, there are no changes to any JSON value. As an exception, a `#!json null`
+value is converted to an empty array or object before the element is added and keeps that type if adding the element
+throws.
+
 ## Exceptions

 1. Throws [`type_error.308`](../../home/exceptions.md#jsonexceptiontype_error308) when called on a type other than
@@ -70,6 +70,9 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. The function can throw the following exceptions:
    - Throws [`type_error.305`](../../home/exceptions.md#jsonexceptiontype_error305) if the JSON value is not an array
      or null; in that case, using the `[]` operator with an index makes no sense.
+    - Throws `#!cpp std::length_error` if `idx` equals the maximum value of `size_type`; the array is left unchanged.
+      (This is the one index for which growing the array to hold it cannot be expressed as a `size_type` size, the same
+      way an oversized [`resize`](https://en.cppreference.com/w/cpp/container/vector/resize) throws.)
 2. The function can throw the following exceptions:
    - Throws [`type_error.305`](../../home/exceptions.md#jsonexceptiontype_error305) if the JSON value is not an object
      or null; in that case, using the `[]` operator with a key makes no sense.
@@ -86,6 +89,9 @@ Strong exception safety: if an exception occurs, the original value stays intact
    - Throws [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) if an array index in the passed
      JSON pointer `ptr` exceeds the range of `size_type` (e.g., on 32-bit platforms).

+    For the **const** version, an object key or array index in `ptr` that does not exist is not reported by an
+    exception, but is undefined behavior (see the notes below). Use [`at`](at.md) for checked access.
+
 ## Complexity

 1. Constant if `idx` is in the range of the array. Otherwise, linear in `idx - size()`.
@@ -100,9 +106,12 @@ Strong exception safety: if an exception occurs, the original value stays intact
    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.
+    1. If the element at index `idx` does not exist, the behavior is undefined and is **guarded by a
+       [runtime assertion](../../features/assertions.md)**!
    2. If the element with key `key` does not exist, the behavior is undefined and is **guarded by a
       [runtime assertion](../../features/assertions.md)**!
+    3. If the JSON pointer `ptr` refers to an object key or an array index that does not exist, the behavior is
+       undefined and is **guarded by a [runtime assertion](../../features/assertions.md)**!

 1. The non-const version may add values: If `idx` is beyond the range of the array (i.e., `idx >= size()`), then the
   array is silently filled up with `#!json null` values to make `idx` a valid reference to the last stored element. In
@@ -133,6 +142,18 @@ Strong exception safety: if an exception occurs, the original value stays intact
        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).

+!!! warning "Deprecation"
+
+    Overload (4) also accepts a [`json_pointer`](../json_pointer/index.md) whose template argument is a `basic_json`
+    specialization (e.g., `nlohmann::json_pointer<nlohmann::json>`) instead of a string type. This is deprecated since
+    version 3.11.0 and will be removed in a future major version; use `basic_json::json_pointer` (for `json`,
+    `nlohmann::json_pointer<std::string>`) instead.
+
+    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
+    function.
+
+    See the [migration guide](../../integration/migration_guide.md#json-pointers) for how to update existing code.
+
 ## Examples

 ??? example "Example: (1) access specified array element"
@@ -257,9 +278,12 @@ Strong exception safety: if an exception occurs, the original value stays intact

 ## Version history

-1. Added in version 1.0.0.
+1. Added in version 1.0.0. Fixed in version 3.13.0 to throw `#!cpp std::length_error` instead of emptying the array and
+   accessing it out of bounds when `idx` equals the maximum value of `size_type`. A missing index in the const version
+   is guarded by a runtime assertion since version 3.13.0.
 2. Added in version 1.0.0. Added overloads for `T* key` in version 1.1.0. Removed overloads for `T* key` (replaced by 3)
   in version 3.11.0.
 3. Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept `std::string_view`-convertible keys, as
   already supported by [`at`](at.md), [`value`](value.md), [`find`](find.md), and other lookup functions.
-4. Added in version 2.0.0.
+4. Added in version 2.0.0. A missing array index in the const version is guarded by a runtime assertion since
+   version 3.13.0.
@@ -17,6 +17,11 @@ Implicit type conversion between the JSON value and a compatible value. The call

 copy of the JSON value, converted to `ValueType`

+## Exception safety
+
+Depends on what `json_serializer<ValueType>` `from_json()` method throws; the JSON value itself is never modified,
+since `#!cpp operator ValueType()` is a `#!cpp const` member function that only calls [`get()`](get.md).
+
 ## Exceptions

 Depends on what `json_serializer<ValueType>` `from_json()` method throws
@@ -56,6 +61,8 @@ Linear in the size of the JSON value.
    [`JSON_USE_IMPLICIT_CONVERSIONS`](../macros/json_use_implicit_conversions.md) to `0` and replace any implicit
    conversions with calls to [`get`](../basic_json/get.md).

+    See the [migration guide](../../integration/migration_guide.md#replace-implicit-conversions) for how to update existing code.
+
 ## Examples

 ??? example
@@ -63,7 +70,7 @@ Linear in the size of the JSON value.
    The example below shows several conversions from JSON values to other types. There are a few things to note: (1)
    Floating-point numbers can be converted to integers, (2) A JSON array can be converted to a standard
    `std::vector<short>`, (3) A JSON object can be converted to C++ associative containers such as
-    `std::unordered_map<std::string, json>`.
+    `std::map<std::string, json>`.
        
    ```cpp
    --8<-- "examples/operator__ValueType.cpp"
@@ -5,17 +5,17 @@
 bool operator==(const_reference lhs, const_reference rhs) noexcept;   // (1)

 template<typename ScalarType>
-bool operator==(const_reference lhs, const ScalarType rhs) noexcept;  // (2)
+bool operator==(const_reference lhs, const ScalarType rhs) noexcept(/* see below */); // (2)

 template<typename ScalarType>
-bool operator==(ScalarType lhs, const const_reference rhs) noexcept;  // (2)
+bool operator==(ScalarType lhs, const const_reference rhs) noexcept(/* see below */); // (2)

 // since C++20
 class basic_json {
    bool operator==(const_reference rhs) const noexcept;              // (1)

    template<typename ScalarType>
-    bool operator==(ScalarType rhs) const noexcept;                   // (2)
+    bool operator==(ScalarType rhs) const noexcept(/* see below */); // (2)
 };
 ```

@@ -46,7 +46,12 @@ whether the values `lhs`/`*this` and `rhs` are equal

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -134,7 +139,7 @@ Linear.

 ## Examples

-??? example
+??? example "Example: (1) compare JSON values"

    The example demonstrates comparing several JSON types.
        
@@ -148,7 +153,7 @@ Linear.
    --8<-- "examples/operator__equal.output"
    ```

-??? example
+??? example "Example: (2) compare JSON values with `#!cpp nullptr`"

    The example demonstrates comparing several JSON types against the null pointer (JSON `#!json null`).
        
@@ -171,3 +176,4 @@ Linear.

 1. Added in version 1.0.0. Added C++20 member functions in version 3.11.0.
 2. Added in version 1.0.0. Added C++20 member functions in version 3.11.0.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -5,10 +5,10 @@
 bool operator>=(const_reference lhs, const_reference rhs) noexcept;   // (1)

 template<typename ScalarType>
-bool operator>=(const_reference lhs, const ScalarType rhs) noexcept;  // (2)
+bool operator>=(const_reference lhs, const ScalarType rhs) noexcept(/* see below */); // (2)

 template<typename ScalarType>
-bool operator>=(ScalarType lhs, const const_reference rhs) noexcept;  // (2)
+bool operator>=(ScalarType lhs, const const_reference rhs) noexcept(/* see below */); // (2)
 ```

 1. Compares whether one JSON value `lhs` is greater than or equal to another JSON value `rhs` according to the following
@@ -39,7 +39,12 @@ whether `lhs` is greater than or equal to `rhs`

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -60,6 +65,16 @@ Linear.
    Since C++20 overload resolution will consider the _rewritten candidate_ generated from
    [`operator<=>`](operator_spaceship.md).

+!!! warning "Deprecation"
+
+    If [`JSON_USE_LEGACY_DISCARDED_VALUE_COMPARISON`](../macros/json_use_legacy_discarded_value_comparison.md) is
+    defined to `1`, the library declares a member `#!cpp bool operator>=(const_reference rhs) const noexcept` in
+    C++20 mode to emulate the legacy comparison of discarded values. This member is deprecated since version 3.11.0,
+    together with the legacy comparison behavior.
+
+    See the [migration guide](../../integration/migration_guide.md#miscellaneous-functions) for how to update existing
+    code.
+
 ## Examples

 ??? example
@@ -84,3 +99,4 @@ Linear.

 1. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
 2. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -5,10 +5,10 @@
 bool operator>(const_reference lhs, const_reference rhs) noexcept;   // (1)

 template<typename ScalarType>
-bool operator>(const_reference lhs, const ScalarType rhs) noexcept;  // (2)
+bool operator>(const_reference lhs, const ScalarType rhs) noexcept(/* see below */); // (2)

 template<typename ScalarType>
-bool operator>(ScalarType lhs, const const_reference rhs) noexcept;  // (2)
+bool operator>(ScalarType lhs, const const_reference rhs) noexcept(/* see below */); // (2)
 ```

 1. Compares whether one JSON value `lhs` is greater than another JSON value `rhs` according to the
@@ -39,7 +39,12 @@ whether `lhs` is greater than `rhs`

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -84,3 +89,4 @@ Linear.

 1. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
 2. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -5,10 +5,10 @@
 bool operator<=(const_reference lhs, const_reference rhs) noexcept;   // (1)

 template<typename ScalarType>
-bool operator<=(const_reference lhs, const ScalarType rhs) noexcept;  // (2)
+bool operator<=(const_reference lhs, const ScalarType rhs) noexcept(/* see below */); // (2)

 template<typename ScalarType>
-bool operator<=(ScalarType lhs, const const_reference rhs) noexcept;  // (2)
+bool operator<=(ScalarType lhs, const const_reference rhs) noexcept(/* see below */); // (2)
 ```

 1. Compares whether one JSON value `lhs` is less than or equal to another JSON value `rhs`
@@ -40,7 +40,12 @@ whether `lhs` is less than or equal to `rhs`

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -61,6 +66,16 @@ Linear.
    Since C++20 overload resolution will consider the _rewritten candidate_ generated from
    [`operator<=>`](operator_spaceship.md).

+!!! warning "Deprecation"
+
+    If [`JSON_USE_LEGACY_DISCARDED_VALUE_COMPARISON`](../macros/json_use_legacy_discarded_value_comparison.md) is
+    defined to `1`, the library declares a member `#!cpp bool operator<=(const_reference rhs) const noexcept` in
+    C++20 mode to emulate the legacy comparison of discarded values. This member is deprecated since version 3.11.0,
+    together with the legacy comparison behavior.
+
+    See the [migration guide](../../integration/migration_guide.md#miscellaneous-functions) for how to update existing
+    code.
+
 ## Examples

 ??? example
@@ -85,3 +100,4 @@ Linear.

 1. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
 2. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -5,10 +5,10 @@
 bool operator<(const_reference lhs, const_reference rhs) noexcept;   // (1)

 template<typename ScalarType>
-bool operator<(const_reference lhs, const ScalarType rhs) noexcept;  // (2)
+bool operator<(const_reference lhs, const ScalarType rhs) noexcept(/* see below */); // (2)

 template<typename ScalarType>
-bool operator<(ScalarType lhs, const const_reference rhs) noexcept;  // (2)
+bool operator<(ScalarType lhs, const const_reference rhs) noexcept(/* see below */); // (2)
 ```

 1. Compares whether one JSON value `lhs` is less than another JSON value `rhs` according to the
@@ -49,7 +49,12 @@ whether `lhs` is less than `rhs`

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -94,3 +99,4 @@ Linear.

 1. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
 2. Added in version 1.0.0. Conditionally removed since C++20 in version 3.11.0.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -5,21 +5,13 @@
 bool operator!=(const_reference lhs, const_reference rhs) noexcept;   // (1)

 template<typename ScalarType>
-bool operator!=(const_reference lhs, const ScalarType rhs) noexcept;  // (2)
+bool operator!=(const_reference lhs, const ScalarType rhs) noexcept(/* see below */); // (2)

 template<typename ScalarType>
-bool operator!=(ScalarType lhs, const const_reference rhs) noexcept;  // (2)
-
-// since C++20
-class basic_json {
-    bool operator!=(const_reference rhs) const noexcept;              // (1)
-
-    template<typename ScalarType>
-    bool operator!=(ScalarType rhs) const noexcept;                   // (2)
-};
+bool operator!=(ScalarType lhs, const const_reference rhs) noexcept(/* see below */); // (2)
 ```

-1. Compares two JSON values for inequality. Returns `#!cpp !(lhs == rhs)` (until C++20) or `#!cpp !(*this == rhs)` (since C++20).
+1. Compares two JSON values for inequality. Returns `#!cpp !(lhs == rhs)`.
    - This means the comparison is simply the logical negation of `operator==`, including for special values like `NaN` and `discarded`.

 2. Compares a JSON value and a scalar or a scalar and a JSON value for inequality by converting the scalar to a JSON
@@ -44,7 +36,12 @@ whether the values `lhs`/`*this` and `rhs` are not equal

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -52,6 +49,11 @@ Linear.

 ## Notes

+!!! note "C++20"
+
+    Since C++20, `basic_json` declares no `operator!=`. The compiler rewrites `#!cpp a != b` as `#!cpp !(a == b)`
+    using [`operator==`](operator_eq.md), so the result is the same as described above.
+
 !!! note "Comparing `NaN` and `discarded`"

    Since `operator!=` is defined as `!(a == b)`, the behavior for special values follows that of `operator==`:
@@ -61,7 +63,7 @@ Linear.

 ## Examples

-??? example
+??? example "Example: (1) compare JSON values"

    The example demonstrates comparing several JSON types.
        
@@ -75,7 +77,7 @@ Linear.
    --8<-- "examples/operator__notequal.output"
    ```

-??? example
+??? example "Example: (2) compare JSON values with `#!cpp nullptr`"

    The example demonstrates comparing several JSON types against the null pointer (JSON `#!json null`).
        
@@ -89,9 +91,16 @@ Linear.
    --8<-- "examples/operator__notequal__nullptr_t.output"
    ```

+## See also
+
+- [operator==](operator_eq.md) comparison: equal
+- [operator<=>](operator_spaceship.md) comparison: 3-way (C++20)
+
 ## Version history

-1. Added in version 1.0.0. Added C++20 member functions in version 3.11.0. Changed in version 3.13.0 to remove 
-   special-casing for `NaN` and `discarded` values; `operator!=` now consistently means `!(a == b)`.
-2. Added in version 1.0.0. Added C++20 member functions in version 3.11.0. Changed in version 3.13.0 to remove
-   special-casing for `NaN` and `discarded` values; `operator!=` now consistently means `!(a == b)`.
+1. Added in version 1.0.0. Added a C++20 member function in version 3.11.0. Changed in version 3.13.0 to remove
+   special-casing for `NaN` and `discarded` values; `operator!=` now consistently means `!(a == b)`. Removed the C++20
+   member function in version 3.13.0; since C++20, the compiler rewrites `a != b` using `operator==`.
+2. Added in version 1.0.0. Changed in version 3.13.0 to remove special-casing for `NaN` and `discarded` values;
+   `operator!=` now consistently means `!(a == b)`. Since C++20, the compiler rewrites `a != b` using `operator==`.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -6,7 +6,7 @@ class basic_json {
    std::partial_ordering operator<=>(const_reference rhs) const noexcept;  // (1)

    template<typename ScalarType>
-    std::partial_ordering operator<=>(const ScalarType rhs) const noexcept; // (2)
+    std::partial_ordering operator<=>(const ScalarType rhs) const noexcept(/* see below */); // (2)
 };
 ```

@@ -39,7 +39,12 @@ the `std::partial_ordering` of the 3-way comparison of `*this` and `rhs`

 ## Exception safety

-No-throw guarantee: this function never throws exceptions.
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee if converting the scalar to a JSON value cannot throw, as for numbers, Booleans, and
+   `#!cpp nullptr`; the function is `#!cpp noexcept` exactly in that case. Otherwise, it throws what the conversion
+   throws, for example `std::bad_alloc` when converting a string, or
+   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) for an enum value not mapped by
+   [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../macros/nlohmann_json_serialize_enum_strict.md).

 ## Complexity

@@ -98,3 +103,4 @@ Linear.

 1. Added in version 3.11.0.
 2. Added in version 3.11.0.
+   Made conditionally `#!cpp noexcept` in version 3.13.0; before, a throwing conversion called `std::terminate`.
@@ -47,6 +47,11 @@ Constant.
    --8<-- "examples/operator__value_t.output"
    ```

+## See also
+
+- [type](type.md) named member function equivalent to this implicit conversion operator
+- [value_t](value_t.md) the enumeration of JSON types
+
 ## Version history

 - Added in version 1.0.0.
@@ -88,7 +88,12 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 ## Exceptions

 - Throws [`parse_error.101`](../../home/exceptions.md#jsonexceptionparse_error101) in case of an unexpected token, or
-  empty input like a null `FILE*` or `char*` pointer.
+  empty input like a null `FILE*` or `char*` pointer, or an `std::istream` without a stream buffer
+  (`#!cpp i.rdbuf() == nullptr`, for instance `#!cpp std::istream(nullptr)`).
+- If reading from an `std::istream` reaches the end of the input and `eofbit` is part of the stream's
+  [`exceptions()`](https://en.cppreference.com/w/cpp/io/basic_ios/exceptions) mask, the `std::ios_base::failure`
+  thrown by the stream itself propagates instead of a `parse_error`, the same as it would for the standard library's
+  own extraction operators.

 ## Complexity

@@ -109,7 +114,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by

 ## Examples

-??? example "Parsing from a character array"
+??? example "Example: (1) parse from a character array"

    The example below demonstrates the `parse()` function reading from an array.

@@ -123,7 +128,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__array__parser_callback_t.output"
    ```

-??? example "Parsing from a string"
+??? example "Example: (1) parse from a string"

    The example below demonstrates the `parse()` function with and without callback function.

@@ -137,7 +142,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__string__parser_callback_t.output"
    ```

-??? example "Parsing from an input stream"
+??? example "Example: (1) parse from an input stream"

    The example below demonstrates the `parse()` function with and without callback function.

@@ -151,7 +156,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__istream__parser_callback_t.output"
    ```

-??? example "Parsing from a contiguous container"
+??? example "Example: (1) parse from a contiguous container"

    The example below demonstrates the `parse()` function reading from a contiguous container.

@@ -165,7 +170,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__contiguouscontainer__parser_callback_t.output"
    ```

-??? example "Parsing from a non-null-terminated string"
+??? example "Example: (2) parse from a non-null-terminated string"

    The example below demonstrates the `parse()` function reading from a string that is not null-terminated.

@@ -179,7 +184,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__pointers.output"
    ```

-??? example "Parsing from an iterator pair"
+??? example "Example: (2) parse from an iterator pair"

    The example below demonstrates the `parse()` function reading from an iterator pair.

@@ -193,7 +198,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__iterator_pair.output"
    ```

-??? example "Effect of `allow_exceptions` parameter"
+??? example "Example: effect of `allow_exceptions` parameter"

    The example below demonstrates the effect of the `allow_exceptions` parameter in the `parse()` function.

@@ -207,7 +212,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/parse__allow_exceptions.output"
    ```

-??? example "Effect of `ignore_comments` parameter"
+??? example "Example: effect of `ignore_comments` parameter"

    The example below demonstrates the effect of the `ignore_comments` parameter in the `parse()` function.

@@ -221,7 +226,7 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/comments.output"
    ```

-??? example "Effect of `ignore_trailing_commas` parameter"
+??? example "Example: effect of `ignore_trailing_commas` parameter"

    The example below demonstrates the effect of the `ignore_trailing_commas` parameter in the `parse()` function.

@@ -254,6 +259,8 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
 - Extended overload (2) to accept heterogeneous iterator+sentinel pairs (C++20 ranges support) in version 3.13.0.
 - `JSON_STRICT_NUL_HANDLING` added in version 3.13.0 to optionally reject a NUL byte in the input instead of treating
  it as end of input; planned to become the default in version 4.0.0.
+- Extended empty-input detection to also cover an `std::istream` without a stream buffer, and fixed a crash
+  (`std::terminate`) when parsing from an `std::istream` with `eofbit` in its exception mask, in version 3.13.0.

 !!! warning "Deprecation"

@@ -263,3 +270,5 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -54,7 +54,7 @@ classDiagram

 ## Notes

-For an input with $n$ bytes, 1 is the index of the first character and $n+1$ is the index of the terminating null byte
+For an input with <i>n</i> bytes, 1 is the index of the first character and <i>n</i>+1 is the index of the terminating null byte
 or the end of file. This also holds true when reading a byte vector for binary formats.

 ## Examples
@@ -24,6 +24,21 @@ The parser callback distinguishes the following events:

 ![Example when certain parse events are triggered](../../images/callback_events.png)

+??? example
+
+    The following code parses a small JSON text with a parser callback that reports every event together with its
+    depth and keeps every value (by always returning `#!cpp true`).
+
+    ```cpp
+    --8<-- "examples/parse_event_t.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/parse_event_t.output"
+    ```
+
 ## See also

 - [parser_callback_t](parser_callback_t.md) callback function type for the parser
@@ -60,7 +60,7 @@ the latter case, it is skipped completely, or replaced by `null` if it is the to

 ## Examples

-??? example
+??? example "Example: skip an object key while parsing"

    The example below demonstrates the `parse()` function with
    and without callback function.
@@ -75,7 +75,7 @@ the latter case, it is skipped completely, or replaced by `null` if it is the to
    --8<-- "examples/parse__string__parser_callback_t.output"
    ```

-??? example
+??? example "Example: how discarded values are removed"

    The example below shows where discarded values are removed. The array and the number are discarded in different
    ways, but in each case the parse result contains neither the value nor its key.
@@ -100,3 +100,6 @@ the latter case, it is skipped completely, or replaced by `null` if it is the to
 - Added in version 1.0.0.
 - Fixed in version 3.13.0 to also remove discarded values from a parent object; before, discarding an array or a value
  stored under an object key left a discarded member behind, which made the parse result serialize to invalid JSON.
+- Fixed in version 3.13.0 so that discarding an array or object at its start event also hides its content from the
+  callback, as documented above; before, the callback was still called for the content, and the key of every member of
+  a discarded object was kept in memory until the parse ended.
@@ -26,10 +26,24 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [`parse_error.104`](../../home/exceptions.md#jsonexceptionparse_error104) if the JSON patch does not consist of
  an array of objects.
 - Throws [`parse_error.105`](../../home/exceptions.md#jsonexceptionparse_error105) if the JSON patch is malformed (e.g.,
-  mandatory attributes are missing); example: `"operation add must have member path"`.
+  mandatory attributes are missing); example: `"operation 'add' must have member 'path'"`.
 - Throws [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if an array index is out of range.
+- Throws [`parse_error.106`](../../home/exceptions.md#jsonexceptionparse_error106) if an array index in a "path" or
+  "from" member begins with '0'; example: `"array index '01' must not begin with '0'"`.
+- Throws [`parse_error.107`](../../home/exceptions.md#jsonexceptionparse_error107) if a "path" or "from" member is not
+  empty and does not begin with a slash (`/`); example: `"JSON pointer must be empty or begin with '/' - was: 'a'"`.
+- Throws [`parse_error.108`](../../home/exceptions.md#jsonexceptionparse_error108) if a tilde (`~`) in a "path" or
+  "from" member is not followed by `0` or `1`; example: `"escape character '~' must be followed with '0' or '1'"`.
+- Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) if an array index in a "path" or
+  "from" member is not a number; example: `"array index 'foo' is not a number"`.
+- Throws [`out_of_range.402`](../../home/exceptions.md#jsonexceptionout_of_range402) if the array index `-` is used
+  where an existing element is required (the "path" of "replace", the "from" of "move" and "copy"); example:
+  `"array index '-' (3) is out of range"`.
 - Throws [`out_of_range.403`](../../home/exceptions.md#jsonexceptionout_of_range403) if a JSON pointer inside the patch
  could not be resolved successfully in the current JSON value; example: `"key baz not found"`.
+- Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a reference token of a JSON
+  pointer inside the patch cannot be resolved, e.g., `-` in a "remove" operation or `1a` for an array; example:
+  `"unresolved reference token '-'"`.
 - Throws [`out_of_range.405`](../../home/exceptions.md#jsonexceptionout_of_range405) if JSON pointer has no parent
  ("add", "remove", "move")
 - Throws [`out_of_range.411`](../../home/exceptions.md#jsonexceptionout_of_range411) if an "add" operation's target
@@ -53,7 +67,7 @@ is thrown. In any case, the original value is not changed: the patch is applied

 ## Examples

-??? example
+??? example "Example: apply a JSON patch"

    The following code shows how a JSON patch is applied to a value.
     
@@ -67,6 +81,21 @@ is thrown. In any case, the original value is not changed: the patch is applied
    --8<-- "examples/patch.output"
    ```

+??? example "Example: out_of_range.414 exception"
+
+    The following code shows how a "move" operation whose "from" location is a proper prefix of its "path" location is
+    rejected, and how the original document is left unchanged because the patch is applied to a copy.
+
+    ```cpp
+    --8<-- "examples/patch__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/patch__exception.output"
+    ```
+
 ## See also

 - [RFC 6902 (JSON Patch)](https://tools.ietf.org/html/rfc6902)
@@ -22,10 +22,24 @@ No guarantees, value may be corrupted by an unsuccessful patch operation.
 - Throws [`parse_error.104`](../../home/exceptions.md#jsonexceptionparse_error104) if the JSON patch does not consist of
  an array of objects.
 - Throws [`parse_error.105`](../../home/exceptions.md#jsonexceptionparse_error105) if the JSON patch is malformed (e.g.,
-  mandatory attributes are missing); example: `"operation add must have member path"`.
+  mandatory attributes are missing); example: `"operation 'add' must have member 'path'"`.
 - Throws [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if an array index is out of range.
+- Throws [`parse_error.106`](../../home/exceptions.md#jsonexceptionparse_error106) if an array index in a "path" or
+  "from" member begins with '0'; example: `"array index '01' must not begin with '0'"`.
+- Throws [`parse_error.107`](../../home/exceptions.md#jsonexceptionparse_error107) if a "path" or "from" member is not
+  empty and does not begin with a slash (`/`); example: `"JSON pointer must be empty or begin with '/' - was: 'a'"`.
+- Throws [`parse_error.108`](../../home/exceptions.md#jsonexceptionparse_error108) if a tilde (`~`) in a "path" or
+  "from" member is not followed by `0` or `1`; example: `"escape character '~' must be followed with '0' or '1'"`.
+- Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) if an array index in a "path" or
+  "from" member is not a number; example: `"array index 'foo' is not a number"`.
+- Throws [`out_of_range.402`](../../home/exceptions.md#jsonexceptionout_of_range402) if the array index `-` is used
+  where an existing element is required (the "path" of "replace", the "from" of "move" and "copy"); example:
+  `"array index '-' (3) is out of range"`.
 - Throws [`out_of_range.403`](../../home/exceptions.md#jsonexceptionout_of_range403) if a JSON pointer inside the patch
  could not be resolved successfully in the current JSON value; example: `"key baz not found"`.
+- Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a reference token of a JSON
+  pointer inside the patch cannot be resolved, e.g., `-` in a "remove" operation or `1a` for an array; example:
+  `"unresolved reference token '-'"`.
 - Throws [`out_of_range.405`](../../home/exceptions.md#jsonexceptionout_of_range405) if JSON pointer has no parent
  ("add", "remove", "move")
 - Throws [`out_of_range.411`](../../home/exceptions.md#jsonexceptionout_of_range411) if an "add" operation's target
@@ -50,7 +64,7 @@ function throws an exception.

 ## Examples

-??? example
+??? example "Example: apply a JSON patch in place"

    The following code shows how a JSON patch is applied to a value.
     
@@ -64,6 +78,22 @@ function throws an exception.
    --8<-- "examples/patch_inplace.output"
    ```

+??? example "Example: out_of_range.403 exception with a partially applied patch"
+
+    The following code shows a patch whose first operation succeeds and whose second operation fails. Because
+    `patch_inplace` applies each operation directly to the value, the first operation's effect is still visible after
+    the exception is caught, unlike [`patch`](patch.md).
+
+    ```cpp
+    --8<-- "examples/patch_inplace__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/patch_inplace__exception.output"
+    ```
+
 ## See also

 - [RFC 6902 (JSON Patch)](https://tools.ietf.org/html/rfc6902)
@@ -44,6 +44,12 @@ invalidates all iterators and all references.
 `init` (in)
 :   an initializer list

+## Exception safety
+
+Strong guarantee: if an exception is thrown, there are no changes to any JSON value. As an exception, a `#!json null`
+value is converted to an empty array or object before the element is added and keeps that type if adding the element
+throws.
+
 ## Exceptions

 1. Throws [`type_error.308`](../../home/exceptions.md#jsonexceptiontype_error308) when called on a type other than
@@ -37,6 +37,13 @@ Constant.
    --8<-- "examples/rbegin.output"
    ```

+## See also
+
+- [rend](rend.md) returns a reverse iterator to one before the first element
+- [crbegin](crbegin.md) returns a const reverse iterator to the last element
+- [begin](begin.md) returns an iterator to the first element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -38,6 +38,13 @@ Constant.
    --8<-- "examples/rend.output"
    ```

+## See also
+
+- [rbegin](rbegin.md) returns a reverse iterator to the last element
+- [crend](crend.md) returns a const reverse iterator to one before the first element
+- [end](end.md) returns an iterator to one past the last element
+- [Iterators](../../features/iterators.md) - the article on iterators
+
 ## Version history

 - Added in version 1.0.0.
@@ -147,3 +147,5 @@ A UTF-8 byte order mark is silently ignored.
    Overload (2) replaces calls to `sax_parse` with a pair of iterators as their first parameter which has been
    deprecated in version 3.8.0. This overload will be removed in version 4.0.0. Please replace all calls like
    `#!cpp sax_parse({ptr, ptr+len});` with `#!cpp sax_parse(ptr, ptr+len);`.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -51,6 +51,11 @@ JSON value which is `1` in the case of a string.
    --8<-- "examples/size.output"
    ```

+## See also
+
+- [empty](empty.md) checks whether the JSON value has no elements
+- [max_size](max_size.md) returns the maximum possible number of elements
+
 ## Version history

 - Added in version 1.0.0.
@@ -28,6 +28,10 @@ type of the JSON value is taken into account to have different hash values for `

    Note the output is platform-dependent.

+## See also
+
+- [operator==](operator_eq.md) compares two JSON values for equality, consistent with equal hash values
+
 ## Version history

 - Added in version 1.0.0.
@@ -30,16 +30,16 @@ JSON class into byte-sized characters during deserialization.

 ## Notes

-#### Default type
+### Default type

 With the default values for `StringType` (`std::string`), the default value for `string_t` is `#!cpp std::string`.

-#### Encoding
+### Encoding

 Strings are stored in UTF-8 encoding. Therefore, functions like `std::string::size()` or `std::string::length()` return
 the number of bytes in the string rather than the number of characters or glyphs.

-#### String comparison
+### String comparison

 [RFC 8259](https://tools.ietf.org/html/rfc8259) states:
 > Software implementations are typically required to test names of object members for equality. Implementations that
@@ -50,15 +50,15 @@ the number of bytes in the string rather than the number of characters or glyphs

 This implementation is interoperable as it does compare strings code unit by code unit.

-#### Storage
+### Storage

 String values are stored as pointers in a `basic_json` type. That is, for any access to string values, a pointer of type
 `string_t*` must be dereferenced.

-#### Cross-`basic_json` conversion requirements
+### Cross-`basic_json` conversion requirements

 When converting a string value from one `basic_json` specialization to another via the
-[converting constructor](basic_json.md#overload-4), the target `string_t` must be directly
+[converting constructor](basic_json.md) (overload 4), the target `string_t` must be directly
 constructible from the source `basic_json`'s `string_t` type. If this requirement is not met, the
 conversion does not fail; instead, the string is silently converted as an array of character codes,
 which is incorrect. See [issue #3425](https://github.com/nlohmann/json/issues/3425) for details
@@ -80,6 +80,12 @@ and an example.
    --8<-- "examples/string_t.output"
    ```

+## See also
+
+- [object_t](object_t.md) the type used to store JSON objects (and their keys, which are also `string_t`)
+- [binary_t](binary_t.md) the type used to store binary values
+- [get_ptr](get_ptr.md) returns a pointer to the stored string value
+
 ## Version history

 - Added in version 1.0.0.
@@ -6,7 +6,9 @@ void swap(reference other) noexcept (
    std::is_nothrow_move_constructible<value_t>::value &&
    std::is_nothrow_move_assignable<value_t>::value &&
    std::is_nothrow_move_constructible<json_value>::value &&
-    std::is_nothrow_move_assignable<json_value>::value
+    std::is_nothrow_move_assignable<json_value>::value &&
+    std::is_nothrow_move_constructible<json_base_class_t>::value &&
+    std::is_nothrow_move_assignable<json_base_class_t>::value
 );

 // (2)
@@ -14,7 +16,9 @@ friend void swap(reference left, reference right) noexcept (
    std::is_nothrow_move_constructible<value_t>::value &&
    std::is_nothrow_move_assignable<value_t>::value &&
    std::is_nothrow_move_constructible<json_value>::value &&
-    std::is_nothrow_move_assignable<json_value>::value
+    std::is_nothrow_move_assignable<json_value>::value &&
+    std::is_nothrow_move_constructible<json_base_class_t>::value &&
+    std::is_nothrow_move_assignable<json_base_class_t>::value
 );

 // (3)
@@ -37,11 +41,15 @@ void swap(typename binary_t::container_type& other);
   individual elements. All iterators and references remain valid. The past-the-end iterator is invalidated. If macro
   [`JSON_DIAGNOSTIC_POSITIONS`](../macros/json_diagnostic_positions.md) is defined to `#!cpp 1`, the
   [`start_pos()`](start_pos.md)/[`end_pos()`](end_pos.md) diagnostic positions are exchanged along with the value.
+   The [`json_base_class_t`](json_base_class_t.md) subobject is exchanged along with the value as well, the same way it
+   is copied or moved by the copy/move constructors and assignment operators.
 2. Exchanges the contents of the JSON value from `left` with those of `right`. Does not invoke any move, copy, or swap
   operations on individual elements. All iterators and references remain valid. The past-the-end iterator is
   invalidated. Implemented as a friend function callable via ADL. If macro
   [`JSON_DIAGNOSTIC_POSITIONS`](../macros/json_diagnostic_positions.md) is defined to `#!cpp 1`, the
   [`start_pos()`](start_pos.md)/[`end_pos()`](end_pos.md) diagnostic positions are exchanged along with the value.
+   The [`json_base_class_t`](json_base_class_t.md) subobject is exchanged along with the value as well, the same way it
+   is copied or moved by the copy/move constructors and assignment operators.
 3. Exchanges the contents of a JSON array with those of `other`. Does not invoke any move, copy, or swap operations on
   individual elements. All iterators and references remain valid. The past-the-end iterator is invalidated. 
 4. Exchanges the contents of a JSON object with those of `other`. Does not invoke any move, copy, or swap operations on
@@ -65,6 +73,16 @@ void swap(typename binary_t::container_type& other);
 `right` (in, out)
 :   value to exchange the contents with

+## Exception safety
+
+1. No-throw guarantee: this function never throws exceptions.
+2. No-throw guarantee: this function never throws exceptions.
+3. Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+4. Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+5. Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+6. Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+7. Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
+
 ## Exceptions

 1. No-throw guarantee: this function never throws exceptions.
@@ -86,7 +104,7 @@ Constant.

 ## Examples

-??? example "Example: Swap JSON value (1, 2)"
+??? example "Example: (1, 2) swap JSON values"

    The example below shows how JSON values can be swapped with `swap()`.
    
@@ -100,7 +118,7 @@ Constant.
    --8<-- "examples/swap__reference.output"
    ```

-??? example "Example: Swap array (3)"
+??? example "Example: (3) swap array"

    The example below shows how arrays can be swapped with `swap()`.
    
@@ -114,7 +132,7 @@ Constant.
    --8<-- "examples/swap__array_t.output"
    ```

-??? example "Example: Swap object (4)"
+??? example "Example: (4) swap object"

    The example below shows how objects can be swapped with `swap()`.
    
@@ -128,7 +146,7 @@ Constant.
    --8<-- "examples/swap__object_t.output"
    ```

-??? example "Example: Swap string (5)"
+??? example "Example: (5) swap string"

    The example below shows how strings can be swapped with `swap()`.
    
@@ -142,7 +160,7 @@ Constant.
    --8<-- "examples/swap__string_t.output"
    ```

-??? example "Example: Swap binary (6)"
+??? example "Example: (6) swap binary"

    The example below shows how binary values can be swapped with `swap()`.
    
@@ -164,8 +182,8 @@ Constant.

 ## Version history

-1. Since version 1.0.0.
-2. Since version 1.0.0.
+1. Since version 1.0.0. Exchanges the `json_base_class_t` subobject along with the value since version 3.13.0.
+2. Since version 1.0.0. Exchanges the `json_base_class_t` subobject along with the value since version 3.13.0.
 3. Since version 1.0.0.
 4. Since version 1.0.0.
 5. Since version 1.0.0.
@@ -5,15 +5,18 @@
 static std::vector<std::uint8_t> to_bjdata(const basic_json& j,
                                           const bool use_size = false,
                                           const bool use_type = false,
-                                           const bjdata_version_t version = bjdata_version_t::draft2);
+                                           const bjdata_version_t version = bjdata_version_t::draft2,
+                                           const error_handler_t error_handler = error_handler_t::keep);

 // (2)
 static void to_bjdata(const basic_json& j, detail::output_adapter<std::uint8_t> o,
                      const bool use_size = false, const bool use_type = false,
-                      const bjdata_version_t version = bjdata_version_t::draft2);
+                      const bjdata_version_t version = bjdata_version_t::draft2,
+                      const error_handler_t error_handler = error_handler_t::keep);
 static void to_bjdata(const basic_json& j, detail::output_adapter<char> o,
                      const bool use_size = false, const bool use_type = false,
-                      const bjdata_version_t version = bjdata_version_t::draft2);
+                      const bjdata_version_t version = bjdata_version_t::draft2,
+                      const error_handler_t error_handler = error_handler_t::keep);
 ```

 Serializes a given JSON value `j` to a byte vector using the BJData (Binary JData) serialization format. BJData aims to
@@ -43,6 +46,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 :   which version of BJData to use (see note on "Binary values" on [BJData](../../features/binary_formats/bjdata.md));
 optional, `#!cpp bjdata_version_t::draft2` by default.

+`error_handler` (in)
+:   how to treat a string or object key in `j` that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    The default, `keep`, writes the ill-formed bytes to the output as is, as every version of `to_bjdata` did before
+    this parameter was added; `strict` throws; `replace`/`ignore` sanitize it the same way [`dump`](dump.md) would.
+    If [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled, the default is `strict` instead.
+
 ## Return value

 1. BJData serialization as byte vector
@@ -55,7 +64,10 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 ## Exceptions

 - Throws [`other_error.502`](../../home/exceptions.md#jsonexceptionother_error502) if `use_type` is true and `use_size`
-  is false.
+  is false, and `j` contains a non-empty array, object, or binary value.
+- Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if a string or object key in `j` is
+  not valid UTF-8 and `error_handler` is `strict` (the default only if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled)

 ## Complexity

@@ -63,7 +75,7 @@ Linear in the size of the JSON value `j`.

 ## Examples

-??? example
+??? example "Example: serialize a JSON value to BJData"

    The example shows the serialization of a JSON value to a byte vector in BJData format.
     
@@ -77,6 +89,21 @@ Linear in the size of the JSON value `j`.
    --8<-- "examples/to_bjdata.output"
    ```

+??? example "Example: other_error.502 exception"
+
+    The example shows how requesting type annotations (`use_type`) without size annotations (`use_size`) throws an
+    exception, because type-optimized containers can only be read back with a preceding size.
+
+    ```cpp
+    --8<-- "examples/to_bjdata__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/to_bjdata__exception.output"
+    ```
+
 ## See also

 - [from_bjdata](from_bjdata.md) create a JSON value from an input in BJData format
@@ -89,4 +116,7 @@ Linear in the size of the JSON value `j`.
 ## Version history

 - Added in version 3.11.0.
- BJData version parameter (for draft3 binary encoding) added in version 3.12.0.
+- BJData version parameter (for draft3 binary encoding) added in version 3.12.0.
+- Added `error_handler` parameter in version 3.13.0. Its default, `keep`, writes the bytes of a string or object key
+  that is not valid UTF-8 unchanged, as before; `strict` (the default if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316`.
@@ -48,7 +48,7 @@ Linear in the size of the JSON value `j`.

 ## Examples

-??? example
+??? example "Example: serialize a JSON value to BON8"

    The example shows the serialization of a JSON value to a byte vector in BON8 format.
     
@@ -62,6 +62,21 @@ Linear in the size of the JSON value `j`.
    --8<-- "examples/to_bon8.output"
    ```

+??? example "Example: type_error.316 exception"
+
+    The example shows how serializing a string that is not valid UTF-8 throws an exception, because BON8 stores strings
+    as UTF-8.
+
+    ```cpp
+    --8<-- "examples/to_bon8__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/to_bon8__exception.output"
+    ```
+
 ## See also

 - [from_bon8](from_bon8.md) create a JSON value from an input in BON8 format
@@ -2,11 +2,14 @@

 ```cpp
 // (1)
-static std::vector<std::uint8_t> to_bson(const basic_json& j);
+static std::vector<std::uint8_t> to_bson(const basic_json& j,
+                                         const error_handler_t error_handler = error_handler_t::keep);

 // (2)
-static void to_bson(const basic_json& j, detail::output_adapter<std::uint8_t> o);
-static void to_bson(const basic_json& j, detail::output_adapter<char> o);
+static void to_bson(const basic_json& j, detail::output_adapter<std::uint8_t> o,
+                    const error_handler_t error_handler = error_handler_t::keep);
+static void to_bson(const basic_json& j, detail::output_adapter<char> o,
+                    const error_handler_t error_handler = error_handler_t::keep);
 ```

 BSON (Binary JSON) is a binary format in which zero or more ordered key/value pairs are stored as a single entity (a
@@ -25,6 +28,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `o` (in)
 :   output adapter to write serialization to

+`error_handler` (in)
+:   how to treat a string or object key in `j` that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    The default, `keep`, writes the ill-formed bytes to the output as is, as every version of `to_bson` did before
+    this parameter was added; `strict` throws; `replace`/`ignore` sanitize it the same way [`dump`](dump.md) would.
+    If [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled, the default is `strict` instead.
+
 ## Return value

 1. BSON serialization as a byte vector
@@ -43,6 +52,12 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [`out_of_range.412`](../../home/exceptions.md#jsonexceptionout_of_range412) if the length of a document, array,
  string, or binary value exceeds the range of the 32-bit BSON length field; example:
  `"BSON length 2147483661 exceeds maximum of 2147483647"`
+- Throws [`out_of_range.415`](../../home/exceptions.md#jsonexceptionout_of_range415) if the subtype of a binary value
+  exceeds 255, the maximum of the BSON binary subtype; example:
+  `"subtype 70000 is too large for the BSON binary subtype (max 255)"`
+- Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if a string or object key is
+  not valid UTF-8 and `error_handler` is `strict` (the default only if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled)

 ## Complexity

@@ -51,7 +66,7 @@ pass before anything is written.

 ## Examples

-??? example
+??? example "Example: serialize a JSON value to BSON"

    The example shows the serialization of a JSON value to a byte vector in BSON format.
     
@@ -65,6 +80,21 @@ pass before anything is written.
    --8<-- "examples/to_bson.output"
    ```

+??? example "Example: out_of_range.409 exception"
+
+    The example shows how serializing a JSON object whose key contains a null byte (U+0000) throws an exception, because
+    BSON keys are null-terminated C strings and cannot contain U+0000 themselves.
+
+    ```cpp
+    --8<-- "examples/to_bson__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/to_bson__exception.output"
+    ```
+
 ## See also

 - [from_bson](from_bson.md) create a JSON value from an input in BSON format
@@ -77,4 +107,10 @@ pass before anything is written.
 ## Version history

 - Added in version 3.4.0.
+- Throws `out_of_range.412` and `out_of_range.415` since version 3.13.0.
 - Linear in the size of `j`, and no longer limited by the call stack for deeply nested values, since version 3.13.0.
+- `out_of_range.415` is now detected before anything is written, like the other exceptions above, since version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0. Its default, `keep`, writes the bytes of a string or object key
+  that is not valid UTF-8 unchanged, as before; `strict` (the default if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316` before anything
+  is written.
@@ -2,11 +2,14 @@

 ```cpp
 // (1)
-static std::vector<std::uint8_t> to_cbor(const basic_json& j);
+static std::vector<std::uint8_t> to_cbor(const basic_json& j,
+                                          const error_handler_t error_handler = error_handler_t::keep);

 // (2)
-static void to_cbor(const basic_json& j, detail::output_adapter<std::uint8_t> o);
-static void to_cbor(const basic_json& j, detail::output_adapter<char> o);
+static void to_cbor(const basic_json& j, detail::output_adapter<std::uint8_t> o,
+                     const error_handler_t error_handler = error_handler_t::keep);
+static void to_cbor(const basic_json& j, detail::output_adapter<char> o,
+                     const error_handler_t error_handler = error_handler_t::keep);
 ```

 Serializes a given JSON value `j` to a byte vector using the CBOR (Concise Binary Object Representation) serialization
@@ -26,6 +29,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `o` (in)
 :   output adapter to write serialization to

+`error_handler` (in)
+:   how to treat a string or object key in `j` that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    The default, `keep`, writes the ill-formed bytes to the output as is, as every version of `to_cbor` did before
+    this parameter was added; `strict` throws; `replace`/`ignore` sanitize it the same way [`dump`](dump.md) would.
+    If [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled, the default is `strict` instead.
+
 ## Return value

 1. CBOR serialization as a byte vector
@@ -35,6 +44,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../

 Strong guarantee: if an exception is thrown, there are no changes in the JSON value.

+## Exceptions
+
+- Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if a string or object key in `j` is
+  not valid UTF-8 and `error_handler` is `strict` (the default only if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled)
+
 ## Complexity

 Linear in the size of the JSON value `j`.
@@ -68,3 +83,6 @@ Linear in the size of the JSON value `j`.

 - Added in version 2.0.9.
 - Compact representation of floating-point numbers added in version 3.8.0.
+- Added `error_handler` parameter in version 3.13.0. Its default, `keep`, writes the bytes of a string or object key
+  that is not valid UTF-8 unchanged, as before; `strict` (the default if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316`.
@@ -2,11 +2,14 @@

 ```cpp
 // (1)
-static std::vector<std::uint8_t> to_msgpack(const basic_json& j);
+static std::vector<std::uint8_t> to_msgpack(const basic_json& j,
+                                            const error_handler_t error_handler = error_handler_t::keep);

 // (2)
-static void to_msgpack(const basic_json& j, detail::output_adapter<std::uint8_t> o);
-static void to_msgpack(const basic_json& j, detail::output_adapter<char> o);
+static void to_msgpack(const basic_json& j, detail::output_adapter<std::uint8_t> o,
+                       const error_handler_t error_handler = error_handler_t::keep);
+static void to_msgpack(const basic_json& j, detail::output_adapter<char> o,
+                       const error_handler_t error_handler = error_handler_t::keep);
 ```

 Serializes a given JSON value `j` to a byte vector using the MessagePack serialization format. MessagePack is a binary
@@ -25,6 +28,13 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 `o` (in)
 :   output adapter to write serialization to

+`error_handler` (in)
+:   how to treat a string or object key in `j` that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    The default, `keep`, writes the ill-formed bytes to the output as is, as every version of `to_msgpack` did before
+    this parameter was added and as the MessagePack specification allows; `strict` throws; `replace`/`ignore` sanitize
+    it the same way [`dump`](dump.md) would. Unlike the other binary writers, the default stays `keep` even if
+    [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled.
+
 ## Return value

 1. MessagePack serialization as a byte vector
@@ -42,6 +52,8 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [`out_of_range.415`](../../home/exceptions.md#jsonexceptionout_of_range415) if the subtype of a binary value
  exceeds 255, the maximum of the MessagePack ext type; example:
  `"subtype 70000 is too large for the MessagePack ext type (max 255)"`
+- Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if a string or object key in `j` is
+  not valid UTF-8 and `error_handler` is `strict`

 ## Complexity

@@ -49,7 +61,7 @@ Linear in the size of the JSON value `j`.

 ## Examples

-??? example
+??? example "Example: serialize a JSON value to MessagePack"

    The example shows the serialization of a JSON value to a byte vector in MessagePack format.
     
@@ -63,6 +75,21 @@ Linear in the size of the JSON value `j`.
    --8<-- "examples/to_msgpack.output"
    ```

+??? example "Example: out_of_range.415 exception"
+
+    The example shows how serializing a binary value whose subtype exceeds 255 throws an exception, because the
+    MessagePack ext type stores the subtype in a single byte.
+
+    ```cpp
+    --8<-- "examples/to_msgpack__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/to_msgpack__exception.output"
+    ```
+
 ## See also

 - [from_msgpack](from_msgpack.md) create a JSON value from an input in MessagePack format
@@ -76,3 +103,8 @@ Linear in the size of the JSON value `j`.

 - Added in version 2.0.9.
 - Throws `out_of_range.412` and `out_of_range.415` since version 3.13.0.
+- Added `error_handler` parameter in version 3.13.0. Its default, `keep`, writes the bytes of a string or object key
+  that is not valid UTF-8 unchanged, as before.
+- Fixed in version 3.13.0 to serialize `number_integer_t`/`number_unsigned_t` pairs of different width correctly;
+  before, integers could be serialized with the wrong value if `number_integer_t` was narrower than
+  `number_unsigned_t`.
@@ -10,7 +10,8 @@ This function implements a user-defined to_string for JSON objects.
 ## Template parameters

 `BasicJsonType`
-:   a specialization of [`basic_json`](index.md)
+:   a specialization of [`basic_json`](index.md) whose [`string_t`](string_t.md) is convertible to `#!cpp std::string`;
+    for other string types, use [`dump`](dump.md), which returns a `string_t`

 ## Return value

@@ -4,13 +4,16 @@
 // (1)
 static std::vector<std::uint8_t> to_ubjson(const basic_json& j,
                                           const bool use_size = false,
-                                           const bool use_type = false);
+                                           const bool use_type = false,
+                                           const error_handler_t error_handler = error_handler_t::keep);

 // (2)
 static void to_ubjson(const basic_json& j, detail::output_adapter<std::uint8_t> o,
-                      const bool use_size = false, const bool use_type = false);
+                      const bool use_size = false, const bool use_type = false,
+                      const error_handler_t error_handler = error_handler_t::keep);
 static void to_ubjson(const basic_json& j, detail::output_adapter<char> o,
-                      const bool use_size = false, const bool use_type = false);
+                      const bool use_size = false, const bool use_type = false,
+                      const error_handler_t error_handler = error_handler_t::keep);
 ```

 Serializes a given JSON value `j` to a byte vector using the UBJSON (Universal Binary JSON) serialization format. UBJSON
@@ -36,6 +39,12 @@ The exact mapping and its limitations are described on a [dedicated page](../../
 :   whether to add type annotations to container types (must be combined with `#!cpp use_size = true`); optional,
    `#!cpp false` by default.

+`error_handler` (in)
+:   how to treat a string or object key in `j` that is not valid UTF-8; see [`error_handler_t`](error_handler_t.md).
+    The default, `keep`, writes the ill-formed bytes to the output as is, as every version of `to_ubjson` did before
+    this parameter was added; `strict` throws; `replace`/`ignore` sanitize it the same way [`dump`](dump.md) would.
+    If [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled, the default is `strict` instead.
+
 ## Return value

 1. UBJSON serialization as a byte vector
@@ -48,7 +57,10 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 ## Exceptions

 - Throws [`other_error.502`](../../home/exceptions.md#jsonexceptionother_error502) if `use_type` is true and `use_size`
-  is false.
+  is false, and `j` contains a non-empty array, object, or binary value.
+- Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if a string or object key in `j` is
+  not valid UTF-8 and `error_handler` is `strict` (the default only if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled)

 ## Complexity

@@ -56,7 +68,7 @@ Linear in the size of the JSON value `j`.

 ## Examples

-??? example
+??? example "Example: serialize a JSON value to UBJSON"

    The example shows the serialization of a JSON value to a byte vector in UBJSON format.
     
@@ -70,6 +82,21 @@ Linear in the size of the JSON value `j`.
    --8<-- "examples/to_ubjson.output"
    ```

+??? example "Example: other_error.502 exception"
+
+    The example shows how requesting type annotations (`use_type`) without size annotations (`use_size`) throws an
+    exception, because type-optimized containers can only be read back with a preceding size.
+
+    ```cpp
+    --8<-- "examples/to_ubjson__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/to_ubjson__exception.output"
+    ```
+
 ## See also

 - [from_ubjson](from_ubjson.md) create a JSON value from an input in UBJSON format
@@ -82,3 +109,6 @@ Linear in the size of the JSON value `j`.
 ## Version history

 - Added in version 3.1.0.
+- Added `error_handler` parameter in version 3.13.0. Its default, `keep`, writes the bytes of a string or object key
+  that is not valid UTF-8 unchanged, as before; `strict` (the default if
+  [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316`.
@@ -47,6 +47,12 @@ Constant.
    --8<-- "examples/type.output"
    ```

+## See also
+
+- [operator value_t](operator_value_t.md) implicit conversion operator equivalent to this named member function
+- [type_name](type_name.md) returns the type as a string, for use in error messages
+- [value_t](value_t.md) the enumeration of JSON types
+
 ## Version history

 - Added in version 1.0.0.
@@ -52,6 +52,11 @@ Constant.
    --8<-- "examples/type_name.output"
    ```

+## See also
+
+- [type](type.md) returns the type of the JSON value
+- [value_t](value_t.md) the enumeration of JSON types
+
 ## Version history

 - Added in version 1.0.0.
@@ -27,8 +27,17 @@ The function can throw the following exceptions:
 - Throws [`type_error.315`](../../home/exceptions.md#jsonexceptiontype_error315) if object values are not primitive
 - Throws [`type_error.313`](../../home/exceptions.md#jsonexceptiontype_error313) if a key (JSON pointer) leads to a
  conflicting nesting; example: `"invalid value to unflatten"`
+- Throws [`parse_error.106`](../../home/exceptions.md#jsonexceptionparse_error106) if an array index in a key begins
+  with '0'; example: `"array index '01' must not begin with '0'"`
+- Throws [`parse_error.107`](../../home/exceptions.md#jsonexceptionparse_error107) if a key is not empty and does not
+  begin with a slash (`/`); example: `"JSON pointer must be empty or begin with '/' - was: 'a'"`
+- Throws [`parse_error.108`](../../home/exceptions.md#jsonexceptionparse_error108) if a tilde (`~`) in a key is not
+  followed by `0` or `1`; example: `"escape character '~' must be followed with '0' or '1'"`
 - Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) if an array index in a key is not a
  number; example: `"array index 'one' is not a number"`
+- Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a level becomes an array
+  (because one of its keys is `0`) and another key at that level cannot be an array index; example:
+  `"unresolved reference token 'x'"`

 ## Complexity

@@ -59,9 +59,15 @@ Basic guarantee: if an exception is thrown during the operation, the JSON value
 1. O(N*log(size() + N)), where N is the number of elements to insert.
 2. O(N*log(size() + N)), where N is the number of elements to insert.

+## Notes
+
+The argument `j` (or, for overload (2), the range `[first, last)`) may be `#!cpp *this` itself or refer to a value
+contained in `#!cpp *this` (for example, a subobject returned by `#!cpp (*this)[key]`); it is read as it was when
+`update()` was called, before any modification of `#!cpp *this`.
+
 ## Examples

-??? example
+??? example "Example: (1) update with another object"

    The example shows how `update()` is used.
    
@@ -75,7 +81,7 @@ Basic guarantee: if an exception is thrown during the operation, the JSON value
    --8<-- "examples/update.output"
    ```

-??? example
+??? example "Example: (2) update with an iterator range"

    The example shows how `update()` is used.
    
@@ -89,7 +95,7 @@ Basic guarantee: if an exception is thrown during the operation, the JSON value
    --8<-- "examples/update__range.output"
    ```

-??? example
+??? example "Example: (1) merge user settings into default settings"

    One common use case for this function is the handling of user settings. Assume your application can be configured in
    some aspects:
@@ -155,3 +161,5 @@ Basic guarantee: if an exception is thrown during the operation, the JSON value

 - Added in version 3.0.0.
 - Added `merge_objects` parameter in 3.10.5.
+- Fixed use of freed or relocated memory when the argument is `#!cpp *this` or refers to a value contained in
+  `#!cpp *this`, in version 3.13.0.
@@ -52,6 +52,14 @@ This is equivalent to Python's `dict.get(key, default)`.
    - Unlike [`operator[]`](operator[].md), this function does not implicitly add an element to the position defined by
     `key`/`ptr` key. This function is furthermore also applicable to const objects.

+!!! note "Integer keys"
+
+    Calling this function with an integer `key` argument (for example, `#!cpp value(0, 1)`) does not compile in
+    C++11, where `object_comparator_t` is not transparent: such an argument would otherwise implicitly convert to a
+    null `#!cpp const char*` and, from there, cause undefined behavior when constructing a `#!cpp std::string` for the
+    object key. To access an array element with a default value, use [`at`](at.md) together with a `#!cpp try`/`#!cpp
+    catch` block, or compare against [`size`](size.md) instead.
+
 ## Template parameters

 `KeyType`
@@ -133,6 +141,18 @@ changes to any JSON value.
    --8<-- "examples/value__return_type.output"
    ```

+!!! warning "Deprecation"
+
+    Overload (3) also accepts a [`json_pointer`](../json_pointer/index.md) whose template argument is a `basic_json`
+    specialization (e.g., `nlohmann::json_pointer<nlohmann::json>`) instead of a string type. This is deprecated since
+    version 3.11.0 and will be removed in a future major version; use `basic_json::json_pointer` (for `json`,
+    `nlohmann::json_pointer<std::string>`) instead.
+
+    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
+    function.
+
+    See the [migration guide](../../integration/migration_guide.md#json-pointers) for how to update existing code.
+
 ## Examples

 ??? example "Example: (1) access specified object element with default value"
@@ -177,6 +197,21 @@ changes to any JSON value.
    --8<-- "examples/value__json_ptr.output"
    ```

+??? example "Example: (1) type_error.302 and type_error.306 exceptions"
+
+    The example below shows how `value()` throws `type_error.302` when the default value's type does not match the type
+    of the stored value, and `type_error.306` when `value()` is called on a JSON value that is not an object.
+
+    ```cpp
+    --8<-- "examples/value__exception.cpp"
+    ```
+
+    Output:
+
+    ```json
+    --8<-- "examples/value__exception.output"
+    ```
+
 ## See also

 - see [`at`](at.md) for access by reference with range checking
@@ -184,8 +219,12 @@ changes to any JSON value.

 ## Version history

-1. Added in version 1.0.0. Changed parameter `default_value` type from `const ValueType&` to `ValueType&&` in version 3.11.0.
-2. Added in version 3.11.0. Made `ValueType` the first template parameter in version 3.11.2.
+1. Added in version 1.0.0. Changed parameter `default_value` type from `const ValueType&` to `ValueType&&` in version
+   3.11.0. Deleted overload for integral key types added in version 3.13.0 to reject such calls at compile time
+   instead of causing undefined behavior at runtime.
+2. Added in version 3.11.0. Made `ValueType` the first template parameter in version 3.11.2. Fixed in version 3.13.0
+   to consistently accept `std::string_view`-convertible keys, as already supported by
+   [`operator[]`](operator[].md), [`at`](at.md), [`find`](find.md), and other lookup functions.
 3. Added in version 2.0.2. Extended to work with arrays in version 3.13.0, including fixing an issue where resolving
   `ptr` through an array unexpectedly threw `out_of_range` instead of returning the resolved element (or
   `default_value`, as documented).
@@ -38,6 +38,16 @@ functions [`is_null`](is_null.md), [`is_object`](is_object.md), [`is_array`](is_

    `discarded` is unordered.

+    ```mermaid
+    flowchart LR
+        A[null] --> B[boolean]
+        B --> C["number_integer / number_unsigned / number_float"]
+        C --> D[object]
+        D --> E[array]
+        E --> F[string]
+        F --> G[binary]
+    ```
+
 !!! note "Types of numbers"

    There are three enumerators for numbers (`number_integer`, `number_unsigned`, and `number_float`) to distinguish
@@ -74,6 +84,14 @@ functions [`is_null`](is_null.md), [`is_object`](is_object.md), [`is_array`](is_
    --8<-- "examples/type.output"
    ```

+## See also
+
+- [type](type.md) return the type of the JSON value
+- [type_name](type_name.md) return the type as string
+- [operator value_t](operator_value_t.md) return the type of the JSON value
+- [is_primitive](is_primitive.md) return whether the type is primitive
+- [is_structured](is_structured.md) return whether the type is structured
+
 ## Version history

 - Added in version 1.0.0.
@@ -16,6 +16,11 @@ Linear.

 <!-- NOLINT Examples -->

+## See also
+
+- [basic_json](basic_json.md) constructs a JSON value
+- [clear](clear.md) clears the content of a JSON value without destroying it
+
 ## Version history

 - Added in version 1.0.0.
@@ -41,6 +41,14 @@ byte_container_with_subtype(container_type&& container, subtype_type subtype);
    --8<-- "examples/byte_container_with_subtype__byte_container_with_subtype.output"
    ```

+## See also
+
+- [set_subtype](set_subtype.md) sets the binary subtype
+- [subtype](subtype.md) return the binary subtype
+- [has_subtype](has_subtype.md) return whether the value has a subtype
+- [binary](../basic_json/binary.md) create a binary JSON value
+- [Binary Values](../../features/binary_values.md) - the article on binary values
+
 ## Version history

 Since version 3.8.0.
@@ -31,6 +31,12 @@ Constant.
    --8<-- "examples/byte_container_with_subtype__clear_subtype.output"
    ```

+## See also
+
+- [set_subtype](set_subtype.md) sets the binary subtype
+- [has_subtype](has_subtype.md) return whether the value has a subtype
+- [subtype](subtype.md) return the binary subtype
+
 ## Version history

 Since version 3.8.0.
@@ -34,6 +34,12 @@ Constant.
    --8<-- "examples/byte_container_with_subtype__has_subtype.output"
    ```

+## See also
+
+- [set_subtype](set_subtype.md) sets the binary subtype
+- [clear_subtype](clear_subtype.md) clears the binary subtype
+- [subtype](subtype.md) return the binary subtype
+
 ## Version history

 Since version 3.8.0.
@@ -22,8 +22,8 @@ specific naming scheme in order to override the binary type.
 ## Member functions

 - [(constructor)](byte_container_with_subtype.md)
- **operator==** - comparison: equal
- **operator!=** - comparison: not equal
+- [**operator==**](operator_eq.md) - comparison: equal
+- [**operator!=**](operator_ne.md) - comparison: not equal
 - [**set_subtype**](set_subtype.md) - sets the binary subtype
 - [**subtype**](subtype.md) - return the binary subtype
 - [**has_subtype**](has_subtype.md) - return whether the value has a subtype
--- a/Show More
+++ b/Show More