Merge remote-tracking branch 'origin/develop' into claude/fix-issue-3989-db7e45

Signed-off-by: Niels Lohmann <mail@nlohmann.me>

.github/CONTRIBUTING.md

@@ -111,6 +111,8 @@ context which existing file needs to be extended, and only very few cases requir
 When fixing a bug, edit `unit-regression3.cpp` and add a section referencing the fixed issue.
 `unit-regression2.cpp` holds the older tests; the two files exist because a single one grew large enough for the
 MinGW linker to fail relocating it, so please keep adding to the smaller file rather than growing the larger one.
+Tests that call `sax_parse` go into `unit-sax_parse.cpp` rather than into a large test file: every call instantiates
+the parser and the binary reader that recover from errors, which grows a test file considerably.
 
 #### Exceptions
 

.github/workflows/check_amalgamation.yml

@@ -163,9 +163,9 @@ jobs:
           python3 $GENERATOR --list-tags
           TAG_COUNT=$(python3 $GENERATOR --list-tags | wc -l)
 
-          python3 $GENERATOR --abi-tags diag,_dp,_ns --abi-tags _diag --output $RUNNER_TEMP/abi_tags.natvis
+          python3 $GENERATOR --abi-tags diag,_dp,_vns --abi-tags _diag --output $RUNNER_TEMP/abi_tags.natvis
-          grep -q '<!-- Namespace nlohmann::json_abi_diag_dp_ns -->' $RUNNER_TEMP/abi_tags.natvis
+          grep -q '<!-- Namespace nlohmann::json_abi_diag_dp_vns -->' $RUNNER_TEMP/abi_tags.natvis
-          grep -q '<!-- Namespace nlohmann::json_abi_diag_dp_ns_v[0-9_]* -->' $RUNNER_TEMP/abi_tags.natvis
+          grep -q '<!-- Namespace nlohmann::json_abi_diag_dp_vns_v[0-9_]* -->' $RUNNER_TEMP/abi_tags.natvis
           test $(grep -c '<!-- Namespace ' $RUNNER_TEMP/abi_tags.natvis) -eq $(( $(grep -c '<!-- Namespace ' nlohmann_json.natvis) + 2 ))
 
           python3 $GENERATOR --all --output $RUNNER_TEMP/all.natvis

.github/workflows/flawfinder.yml

@@ -43,8 +43,8 @@ jobs:
       - name: flawfinder_scan
         uses: david-a-wheeler/flawfinder@c4216b74cf2639ffa98503768bd6e4299b5440c9 # v2.0.20
         with:
-          # single_include/ is generated from include/ and would report every finding twice
+          # single_include/ is omitted: it is generated from include/ and would report every finding twice
-          arguments: "--sarif --exclude '*/single_include/*' ./"
+          arguments: '--sarif ./cmake ./docs ./include ./src ./tests ./tools'
           output: 'flawfinder_results.sarif'
 
       - name: Upload analysis results to GitHub Security tab

BUILD.bazel

@@ -90,7 +90,6 @@ cc_library(
         "include/nlohmann/detail/view/simd.hpp",
         "include/nlohmann/detail/view/string_ref.hpp",
         "include/nlohmann/detail/view/value.hpp",
-        "include/nlohmann/detail/view/view_mode.hpp",
         "include/nlohmann/json.hpp",
         "include/nlohmann/json_fwd.hpp",
         "include/nlohmann/json_literals.hpp",

FILES.md

@@ -309,7 +309,7 @@ The "Check amalgamation" workflow fails if the file is out of date.
 
 The file covers the namespace variants with up to two ABI tags. A Natvis file for other configurations can be
 generated with the `--abi-tags` or `--all` options, for example
-`make natvis NATVIS_ARGS="--abi-tags _diag,_dp,_ns --output my_nlohmann_json.natvis"`; see
+`make natvis NATVIS_ARGS="--abi-tags _diag,_dp,_vns --output my_nlohmann_json.natvis"`; see
 [`tools/generate_natvis`](tools/generate_natvis/README.md). With MSVC, CMake adds the file to the `nlohmann_json`
 target and installs it.
 

Makefile

@@ -120,7 +120,7 @@ $(AMALGAMATED_VIEW_FILE): $(SRCS)
 	tools/amalgamate/amalgamate.py -c tools/amalgamate/config_json_view.json -s . --verbose=yes
 
 NATVIS_VENV=tools/generate_natvis/venv
-# extra options for generate_natvis.py, e.g. NATVIS_ARGS="--abi-tags _diag,_dp,_ns --output my.natvis"
+# extra options for generate_natvis.py, e.g. NATVIS_ARGS="--abi-tags _diag,_dp,_vns --output my.natvis"
 NATVIS_ARGS=
 
 # regenerate nlohmann_json.natvis from the ABI tags and version in include/nlohmann/detail/abi_macros.hpp

README.md

@@ -495,7 +495,7 @@ bool key(string_t& val);
 bool parse_error(std::size_t position, const std::string& last_token, const detail::exception& ex);
 ```
 
-The return value of each function determines whether parsing should proceed.
+The return value of each function determines whether parsing should proceed. For `parse_error`, returning `true` [recovers from the error](https://json.nlohmann.me/features/parsing/error_recovery/): the parser repairs the input and continues.
 
 To implement your own SAX handler, proceed as follows:
 
@@ -503,7 +503,7 @@ To implement your own SAX handler, proceed as follows:
 2. Create an object of your SAX interface class, e.g. `my_sax`.
 3. Call `bool json::sax_parse(input, &my_sax)`; where the first parameter can be any input like a string or an input stream and the second parameter is a pointer to your SAX interface.
 
-Note the `sax_parse` function only returns a `bool` indicating the result of the last executed SAX event. It does not return a  `json` value - it is up to you to decide what to do with the SAX events. Furthermore, no exceptions are thrown in case of a parse error -- it is up to you what to do with the exception object passed to your `parse_error` implementation. Internally, the SAX interface is used for the DOM parser (class `json_sax_dom_parser`) as well as the acceptor (`json_sax_acceptor`), see file [`json_sax.hpp`](https://github.com/nlohmann/json/blob/develop/include/nlohmann/detail/input/json_sax.hpp).
+Note the `sax_parse` function only returns a `bool` indicating whether the input was parsed without errors and no SAX event returned `false`. It does not return a  `json` value - it is up to you to decide what to do with the SAX events. Furthermore, no exceptions are thrown in case of a parse error -- it is up to you what to do with the exception object passed to your `parse_error` implementation. Internally, the SAX interface is used for the DOM parser (class `json_sax_dom_parser`) as well as the acceptor (`json_sax_acceptor`), see file [`json_sax.hpp`](https://github.com/nlohmann/json/blob/develop/include/nlohmann/detail/input/json_sax.hpp).
 
 ### STL-like access
 

docs/mkdocs/docs/api/adl_serializer/from_json.md

@@ -30,7 +30,7 @@ class (either explicitly or via the conversion operators).
 
 ## Return value
 
-1. (none) — the converted value is written to the output parameter `val`.
+1. (none) -- the converted value is written to the output parameter `val`.
 2. the JSON value `j` converted to `TargetType`
 
 ## Examples
@@ -67,9 +67,7 @@ class (either explicitly or via the conversion operators).
 
 ## See also
 
-- [`to_json`](to_json.md) - convert a C++ value to JSON
+- [to_json](to_json.md)
-- [Arbitrary Type Conversions](../../features/arbitrary_types.md) - write your own `from_json` and `to_json` functions
-- [Converting values](../../features/conversions.md) - overview of `get`, `get_to` and implicit conversions
 
 ## Version history
 

docs/mkdocs/docs/api/adl_serializer/index.md

@@ -33,10 +33,10 @@ struct adl_serializer {
 ## See also
 
 - [Arbitrary type conversions](../../features/arbitrary_types.md) - how to make your types convertible
-- [`get`](../basic_json/get.md) - / [`get_to`](../basic_json/get_to.md) - convert a JSON value to a C++ type
+- [**get**](../basic_json/get.md) / [**get_to**](../basic_json/get_to.md) - convert a JSON value to a C++ type
-- [`basic_json`](../basic_json/basic_json.md) - construct a JSON value from a C++ value
+- [**basic_json**](../basic_json/basic_json.md) - construct a JSON value from a C++ value
-- [`NLOHMANN_DEFINE_TYPE_INTRUSIVE`](../macros/nlohmann_define_type_intrusive.md) - generate the conversion functions for a type
+- [**NLOHMANN_DEFINE_TYPE_INTRUSIVE**](../macros/nlohmann_define_type_intrusive.md) - generate the conversion functions for a type
-- [Specializing enum conversion](../../features/enum_conversion.md) - serializing enums as JSON strings
+- [Specializing enum conversion](../../features/enum_conversion.md)
 
 ## Version history
 

docs/mkdocs/docs/api/adl_serializer/to_json.md

@@ -36,9 +36,7 @@ This function is usually called by the constructors of the [basic_json](../basic
 
 ## See also
 
-- [`from_json`](from_json.md) - convert JSON to a C++ value
+- [from_json](from_json.md)
-- [Arbitrary Type Conversions](../../features/arbitrary_types.md) - write your own `from_json` and `to_json` functions
-- [Converting values](../../features/conversions.md) - overview of `get`, `get_to` and implicit conversions
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/accept.md

@@ -148,20 +148,15 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
 
 ## See also
 
-- [`parse`](parse.md) - deserialize from a compatible input
+- [parse](parse.md) - deserialize from a compatible input
-- [`sax_parse`](sax_parse.md) - parse input using the SAX interface
+- [sax_parse](sax_parse.md) - parse input using the SAX interface
-- [`operator>>`](../operator_gtgt.md) - deserialize from stream
+- [operator>>](../operator_gtgt.md) - deserialize from stream
 - [`JSON_STRICT_NUL_HANDLING`](../macros/json_strict_nul_handling.md) - opt in to rejecting a NUL byte in the input
   instead of treating it as end of input
 - [`JSON_DISABLE_STREAM_BULK_SCAN`](../macros/json_disable_stream_bulk_scan.md) - read a `std::istream` one character
   at a time
 - [`JSON_DISABLE_UNLOCKED_FILE_IO`](../macros/json_disable_unlocked_file_io.md) - read a `FILE*` with the locking stdio
   functions
-- [Parsing](../../features/parsing/index.md) - overview of the parsing functions
-- [Comments](../../features/comments.md) - ignore `//` and `/* */` comments while parsing
-- [Trailing Commas](../../features/trailing_commas.md) - accept trailing commas in arrays and objects
-- [Parsing and Exceptions](../../features/parsing/parse_exceptions.md) - handling parse errors and locating them in the input
-- [Parsing Untrusted Input](../../features/parsing/untrusted_input.md) - limits and checks for input you do not control
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/array.md

@@ -29,9 +29,9 @@ Linear in the size of `init`.
 This function is only needed to express two edge cases that cannot be realized with the initializer list constructor
 ([`basic_json(initializer_list_t, bool, value_t)`](basic_json.md)). These cases are:
 
-1. creating an array whose elements are all pairs whose first element is a string — in this case, the initializer list
+1. creating an array whose elements are all pairs whose first element is a string -- in this case, the initializer list
    constructor would create an object, taking the first elements as keys
-2. creating an empty array — passing the empty initializer list to the initializer list constructor yields an empty
+2. creating an empty array -- passing the empty initializer list to the initializer list constructor yields an empty
    object
 
 ## Examples

docs/mkdocs/docs/api/basic_json/array_t.md

@@ -69,12 +69,10 @@ Arrays are stored as pointers in a `basic_json` type. That is, for any access to
 
 ## See also
 
-- [`object_t`](object_t.md) - the type used to store JSON objects
+- [object_t](object_t.md) the type used to store JSON objects
-- [`binary_t`](binary_t.md) - the type used to store binary values
+- [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
+- [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
+- [max_size](max_size.md) returns the maximum possible number of elements
-- [Types](../../features/types/index.md) - how arrays are stored
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `ArrayType` template parameter
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/as_base_class.md

@@ -46,8 +46,7 @@ The function is equivalent to `static_cast<json_base_class_t&>(j)` (or `static_c
 
 ## See also
 
-- [`json_base_class_t`](json_base_class_t.md) - type of the custom base class
+- [json_base_class_t](json_base_class_t.md) - type of the custom base class
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `CustomBaseClass` template parameter
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/at.md

@@ -90,8 +90,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Constant.
 2. Logarithmic in the size of the container.
 3. Logarithmic in the size of the container.
-4. Linear in the number of reference tokens of `ptr`; for each of them, logarithmic in the size of the object, or
+4. Logarithmic in the size of the container.
-   constant for an array.
 
 ## Notes
 
@@ -231,12 +230,10 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
 ## See also
 
-- [Checked access](../../features/element_access/checked_access.md) - element access with range checking
+- documentation on [checked access](../../features/element_access/checked_access.md)
-- [`operator[]`](operator%5B%5D.md) - unchecked access by reference
+- [`operator[]`](operator%5B%5D.md) for unchecked access by reference
-- [`value`](value.md) - access with default value
+- [`value`](value.md) for access with default value
-- [`basic_json_view::at`](../basic_json_view/at.md) - the same access on a zero-copy view
+- [basic_json_view::at](../basic_json_view/at.md) - the same access on a zero-copy view
-- [Element Access](../../features/element_access/index.md) - overview of all ways to access elements
-- [JSON Pointer](../../features/json_pointer.md) - access nested values with a pointer
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/back.md

@@ -57,9 +57,8 @@ Constant.
 
 ## See also
 
-- [`front`](front.md) - to access the first element
+- [front](front.md) to access the first element
-- [`basic_json_view::back`](../basic_json_view/back.md) - the same access on a zero-copy view
+- [basic_json_view::back](../basic_json_view/back.md) - the same access on a zero-copy view
-- [Element Access](../../features/element_access/index.md) - overview of all ways to access elements
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/basic_json.md

@@ -52,7 +52,7 @@ basic_json(basic_json&& other) noexcept;
     The postcondition of this constructor can be restored by calling [`clear()`](clear.md).
 
 2. Create a `#!json null` JSON value. It either takes a null pointer as parameter (explicitly creating `#!json null`)
-   or no parameter (implicitly creating `#!json null`). The passed null pointer itself is not read — it is only used to
+   or no parameter (implicitly creating `#!json null`). The passed null pointer itself is not read -- it is only used to
    choose the right constructor.
 
 3. This is a "catch all" constructor for all compatible JSON types; that is, types for which a `to_json()` method
@@ -113,22 +113,19 @@ basic_json(basic_json&& other) noexcept;
 
     ```mermaid
     flowchart TD
-        A(["initializer_list init"]) --> B{{"empty, or every element is a 2-element<br/>array whose first element is a string?"}}
+        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 -->|"yes"| C{"type_deduction"}
-        B -->|"no"| D{{"type_deduction"}}
+        B -->|"no"| D{"type_deduction"}
         C -->|"true"| OBJ["create object"]
-        C -->|"false"| E{{"manual_type"}}
+        C -->|"false"| E{"manual_type"}
         E -->|"object"| OBJ
         E -->|"array"| ARR["create array"]
         D -->|"true"| ARR
-        D -->|"false"| F{{"manual_type"}}
+        D -->|"false"| F{"manual_type"}
         F -->|"array"| ARR
         F -->|"object"| ERR["throw type_error.301"]
     ```
 
-    <p class="nj-caption" markdown>Decision flow for an initializer list: hexagons are checks, edge labels are their
-    outcomes, and rectangles are the resulting value or exception.</p>
-
     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.
@@ -476,13 +473,12 @@ basic_json(basic_json&& other) noexcept;
 
 ## See also
 
-- [`array`](array.md) - create a JSON array value, forcing array creation from an initializer list even when it looks like
+- [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
+- [object](object.md) create a JSON object value, forcing object creation from an initializer list
-- [`binary`](binary.md) - create a JSON binary array value
+- [binary](binary.md) create a JSON binary array value
-- [`operator=`](operator=.md) - copy assignment operator
+- [operator=](operator=.md) copy assignment operator
 - [Creating JSON values](../../features/creating_values.md) - the article on creating JSON values
-- [Converting values](../../features/conversions.md) - which C++ types can be converted
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/begin.md

@@ -7,12 +7,7 @@ const_iterator begin() const noexcept;
 
 Returns an iterator to the first element.
 
-<div class="nj-fig-wrap" markdown>
+![Illustration from cppreference.com](../../images/range-begin-end.svg)
---8<-- "images/range-begin-end.svg"
-</div>
-
-<p class="nj-caption" markdown>`begin()` points to the first element and `end()` to the position after the last element;
-the dashed cell is the past-the-last position, which must not be dereferenced.</p>
 
 ## Return value
 
@@ -44,12 +39,12 @@ Constant.
 
 ## See also
 
-- [`end`](end.md) - returns an iterator to one past the last element
+- [end](end.md) returns an iterator to one past the last element
-- [`cbegin`](cbegin.md) - returns a const iterator to the first element
+- [cbegin](cbegin.md) returns a const iterator to the first element
-- [`rbegin`](rbegin.md) - returns a reverse iterator to the last 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
+- [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
-- [`basic_json_view::begin`](../basic_json_view/begin.md) - the same iteration on a zero-copy view (in document order,
+- [basic_json_view::begin](../basic_json_view/begin.md) - the same iteration on a zero-copy view (in document order,
   not sorted by key)
 
 ## Version history

docs/mkdocs/docs/api/basic_json/binary.md

@@ -63,11 +63,10 @@ initialization of a binary array type, for backwards compatibility and so it doe
 
 ## See also
 
-- [Binary formats](../../features/binary_formats/index.md) - formats that can store binary values
+- [binary_t](binary_t.md) type for binary values
-- [`binary_t`](binary_t.md) - type for binary values
+- [get_binary](get_binary.md) get a reference to the stored binary value
-- [`get_binary`](get_binary.md) - get a reference to the stored binary value
+- [is_binary](is_binary.md) return whether the value is binary
-- [`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
-- [`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

docs/mkdocs/docs/api/basic_json/binary_t.md

@@ -41,7 +41,7 @@ represent a byte array in modern C++.
     [`byte_container_with_subtype`](../byte_container_with_subtype/index.md) derives directly from it. Its
     `value_type` must additionally be exactly one byte wide (e.g., `std::uint8_t`/`char`/`std::byte`): the binary
     serializers (CBOR, MessagePack, BSON, UBJSON) read and write the container's raw bytes via
-    `reinterpret_cast`, which is only correct for byte-sized elements — a container like
+    `reinterpret_cast`, which is only correct for byte-sized elements -- a container like
     `#!cpp std::vector<std::intptr_t>` will not work as `BinaryType`. The elements must be stored contiguously, and
     the binary readers additionally require `resize()` and `operator[]`. See
     [Template Parameter Requirements](../../features/types/template_parameters.md#binarytype) for the full list.
@@ -90,9 +90,8 @@ type `#!cpp binary_t*` must be dereferenced.
 
 - MessagePack
     - If a subtype is given and the binary array contains exactly 1, 2, 4, 8, or 16 elements, the fixext family (fixext1,
-      fixext2, fixext4, fixext8, fixext16) is used. For other sizes, the ext family (ext8, ext16, ext32) is used. The
+      fixext2, fixext4, fixext8) is used. For other sizes, the ext family (ext8, ext16, ext32) is used. The subtype is
-      subtype is then written as the signed 8-bit ext type: subtypes 128 to 255 map to the negative (reserved) ext
+      then added as a signed 8-bit integer.
-      types, and on reading the ext type is exposed as an unsigned subtype from 0 to 255.
     - If no subtype is given, the bin family (bin8, bin16, bin32) is used.
 
 - BSON
@@ -118,9 +117,7 @@ type `#!cpp binary_t*` must be dereferenced.
 
 ## See also
 
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [byte_container_with_subtype](../byte_container_with_subtype/index.md)
-- [Binary formats](../../features/binary_formats/index.md) - formats that can store binary values
-- [`byte_container_with_subtype`](../byte_container_with_subtype/index.md) - container type used by binary values
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/bjdata_version_t.md

@@ -1,48 +0,0 @@
-# <small>nlohmann::basic_json::</small>bjdata_version_t
-
-```cpp
-enum class bjdata_version_t
-{
-    draft2,
-    draft3
-};
-```
-
-This enumeration is used in [`to_bjdata`](to_bjdata.md) to choose the version of the BJData specification to write:
-
-draft2
-:   BJData Draft 2 (the default). Binary values are written as arrays of `U` integers, and ND-arrays with
-    `"_ArrayType_": "byte"` are written as regular objects, since the `B` marker is not part of Draft 2.
-
-draft3
-:   BJData Draft 3. Binary values are written as `B` elements: as an optimized binary array (`[$B#`) if both `use_size`
-    and `use_type` are set, and as an array of `B`-prefixed elements otherwise. ND-arrays with
-    `"_ArrayType_": "byte"` are written as packed arrays (`[$B#[...]`).
-
-Only the writer is affected by the version. [`from_bjdata`](from_bjdata.md) reads the markers of both drafts.
-
-## Examples
-
-??? example
-
-    The example below shows how the different values of the `bjdata_version_t` influence the serialization of a binary
-    value with [`to_bjdata`](to_bjdata.md).
-
-    ```cpp
-    --8<-- "examples/bjdata_version_t.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/bjdata_version_t.output"
-    ```
-
-## See also
-
-- [to_bjdata](to_bjdata.md) serializes a JSON value to BJData
-- [BJData](../../features/binary_formats/bjdata.md) - the article on the BJData format
-
-## Version history
-
-- Added in version 3.12.0.

docs/mkdocs/docs/api/basic_json/boolean_t.md

@@ -47,9 +47,7 @@ Boolean values are stored directly inside a `basic_json` type.
 
 ## See also
 
-- [`is_boolean`](is_boolean.md) - checks whether the JSON value is a boolean
+- [is_boolean](is_boolean.md) checks whether the JSON value is a boolean
-- [Types](../../features/types/index.md) - how booleans are stored
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `BooleanType` template parameter
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/cbegin.md

@@ -6,12 +6,7 @@ const_iterator cbegin() const noexcept;
 
 Returns an iterator to the first element.
 
-<div class="nj-fig-wrap" markdown>
+![Illustration from cppreference.com](../../images/range-begin-end.svg)
---8<-- "images/range-begin-end.svg"
-</div>
-
-<p class="nj-caption" markdown>`cbegin()` points to the first element, like `begin()`, and `end()` to the position after
-the last element; the dashed cell is the past-the-last position, which must not be dereferenced.</p>
 
 ## Return value
 
@@ -43,11 +38,11 @@ Constant.
 
 ## See also
 
-- [`begin`](begin.md) - returns an iterator to the first element
+- [begin](begin.md) returns an iterator to the first element
-- [`cend`](cend.md) - returns a const iterator to one past the last 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
+- [crbegin](crbegin.md) returns a const reverse iterator to the last element
 - [Iterators](../../features/iterators.md) - the article on iterators
-- [`basic_json_view::cbegin`](../basic_json_view/cbegin.md) - the same iteration on a zero-copy view
+- [basic_json_view::cbegin](../basic_json_view/cbegin.md) - the same iteration on a zero-copy view
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/cbor_tag_handler_t.md

@@ -15,13 +15,11 @@ error
 :   report a parse error in case of a tag (the `from_cbor` overloads throw a `parse_error` exception by default)
 
 ignore
-:   ignore tags (also in front of a text string map key)
+:   ignore tags
 
 store
 :   store tagged byte strings (for bytes 0xd8..0xdb) as binary values with the tag as subtype; other tagged values are
-    read as if the tag were ignored. If several tags precede a byte string, only the tag directly in front of it is
+    read as if the tag were ignored. If several tags precede a byte string, only the innermost one is stored.
-    stored, and only when it has the form 0xd8..0xdb (a tag 0..23 written as 0xc0..0xd7 is skipped). Tags in front of a
-    text string map key are skipped.
 
 ## Examples
 
@@ -42,9 +40,8 @@ store
 
 ## See also
 
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [from_cbor](from_cbor.md) deserializes a JSON value from CBOR
-- [`from_cbor`](from_cbor.md) - deserializes a JSON value from CBOR
+- [input_format_t](input_format_t.md) the enumeration of supported input formats
-- [`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

docs/mkdocs/docs/api/basic_json/cend.md

@@ -6,12 +6,7 @@ const_iterator cend() const noexcept;
 
 Returns an iterator to one past the last element.
 
-<div class="nj-fig-wrap" markdown>
+![Illustration from cppreference.com](../../images/range-begin-end.svg)
---8<-- "images/range-begin-end.svg"
-</div>
-
-<p class="nj-caption" markdown>`cend()` points to the position after the last element, like `end()`, and `begin()` to
-the first element; the dashed cell is the past-the-last position, which must not be dereferenced.</p>
 
 ## Return value
 
@@ -43,11 +38,11 @@ Constant.
 
 ## See also
 
-- [`end`](end.md) - returns an iterator to one past the last element
+- [end](end.md) returns an iterator to one past the last element
-- [`cbegin`](cbegin.md) - returns a const iterator to the first 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
+- [crend](crend.md) returns a const reverse iterator to one before the first element
 - [Iterators](../../features/iterators.md) - the article on iterators
-- [`basic_json_view::cend`](../basic_json_view/cend.md) - the same iteration on a zero-copy view
+- [basic_json_view::cend](../basic_json_view/cend.md) - the same iteration on a zero-copy view
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/clear.md

@@ -54,9 +54,8 @@ All iterators, pointers, and references related to this container are invalidate
 
 ## See also
 
-- [`erase`](erase.md) - removes elements from a JSON value
+- [erase](erase.md) removes elements from a JSON value
-- [`empty`](empty.md) - checks whether the JSON value has no elements
+- [empty](empty.md) checks whether the JSON value has no elements
-- [Modifying values](../../features/modifying_values.md) - the article on modifying values
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/contains.md

@@ -61,18 +61,11 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
 ## Complexity
 
-1. Logarithmic in the size of the JSON object.
+Logarithmic in the size of the JSON object.
-2. Logarithmic in the size of the JSON object.
-3. At most one lookup per reference token of `ptr`, each logarithmic in the size of the container at that level:
-   O(*n* log *m*) for *n* reference tokens and containers of size at most *m*.
-4. Deleted; a call with an integral argument does not compile.
 
 ## Notes
 
-- Overloads (1) and (2) always return `#!cpp false` when executed on a JSON type that is not an object. Overload (3)
+- This method always returns `#!cpp false` when executed on a JSON type that is not an object.
-  also works on arrays and on primitive values: the empty JSON pointer resolves in every JSON value (so
-  `#!cpp json(1).contains(""_json_pointer)` returns `#!cpp true`), and `#!cpp json({1, 2}).contains("/1"_json_pointer)`
-  returns `#!cpp true`.
 - 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
@@ -141,10 +134,9 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
 ## See also
 
-- [`find`](find.md) - find a value in an object
+- [find](find.md) find a value in an object
-- [`count`](count.md) - returns the number of occurrences of a key
+- [count](count.md) returns the number of occurrences of a key
-- [`basic_json_view::contains`](../basic_json_view/contains.md) - the same check on a zero-copy view
+- [basic_json_view::contains](../basic_json_view/contains.md) - the same check on a zero-copy view
-- [Element Access](../../features/element_access/index.md#does-this-key-exist) - how to test whether a key exists
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/count.md

@@ -85,10 +85,9 @@ Logarithmic in the size of the JSON object.
 
 ## See also
 
-- [`find`](find.md) - find a value in an object
+- [find](find.md) find a value in an object
-- [`contains`](contains.md) - checks whether a key exists
+- [contains](contains.md) checks whether a key exists
-- [`basic_json_view::count`](../basic_json_view/count.md) - the same check on a zero-copy view
+- [basic_json_view::count](../basic_json_view/count.md) - the same check on a zero-copy view
-- [Element Access](../../features/element_access/index.md#does-this-key-exist) - how to test whether a key exists
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/crbegin.md

@@ -6,13 +6,7 @@ const_reverse_iterator crbegin() const noexcept;
 
 Returns an iterator to the reverse-beginning; that is, the last element.
 
-<div class="nj-fig-wrap" markdown>
+![Illustration from cppreference.com](../../images/range-rbegin-rend.svg)
---8<-- "images/range-rbegin-rend.svg"
-</div>
-
-<p class="nj-caption" markdown>`crbegin()` points to the last element, like `rbegin()`, and `rend()` to the position
-before the first element. The upper row is the reversed sequence and the lower row the forward sequence; dashed arrows
-link each reverse iterator to the forward iterator it stores, and dashed cells are past-the-last positions.</p>
 
 ## Return value
 
@@ -44,9 +38,9 @@ Constant.
 
 ## See also
 
-- [`crend`](crend.md) - returns a const reverse iterator to one before the first element
+- [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
+- [rbegin](rbegin.md) returns a reverse iterator to the last element
-- [`cbegin`](cbegin.md) - returns a const iterator to the first element
+- [cbegin](cbegin.md) returns a const iterator to the first element
 - [Iterators](../../features/iterators.md) - the article on iterators
 
 ## Version history

docs/mkdocs/docs/api/basic_json/crend.md

@@ -7,13 +7,7 @@ const_reverse_iterator crend() const noexcept;
 Returns an iterator to the reverse-end; that is, one before the first element. This element acts as a placeholder,
 attempting to access it results in undefined behavior.
 
-<div class="nj-fig-wrap" markdown>
+![Illustration from cppreference.com](../../images/range-rbegin-rend.svg)
---8<-- "images/range-rbegin-rend.svg"
-</div>
-
-<p class="nj-caption" markdown>`crend()` points to the position before the first element, like `rend()`, and `rbegin()`
-to the last element. The upper row is the reversed sequence and the lower row the forward sequence; dashed arrows link
-each reverse iterator to the forward iterator it stores, and dashed cells are past-the-last positions.</p>
 
 ## Return value
 
@@ -45,9 +39,9 @@ Constant.
 
 ## See also
 
-- [`crbegin`](crbegin.md) - returns a const reverse iterator to the last element
+- [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
+- [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
+- [cend](cend.md) returns a const iterator to one past the last element
 - [Iterators](../../features/iterators.md) - the article on iterators
 
 ## Version history

docs/mkdocs/docs/api/basic_json/default_object_comparator_t.md

@@ -32,10 +32,8 @@ The actual comparator used depends on [`object_t`](object_t.md) and can be obtai
 
 ## See also
 
-- [`object_comparator_t`](object_comparator_t.md) - the comparator actually used by `object_t`
+- [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
+- [object_t](object_t.md) the type used to store JSON objects
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `ObjectType` template parameter
-- [Object order](../../features/object_order.md) - preserve the insertion order of keys
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/diff.md

@@ -2,28 +2,17 @@
 
 ```cpp
 static basic_json diff(const basic_json& source,
-                       const basic_json& target,
+                       const basic_json& target);
-                       const string_t& path = "");
 ```
 
 Creates a [JSON Patch](http://jsonpatch.com) so that value `source` can be changed into the value `target` by calling
 [`patch`](patch.md) function.
 
-For two JSON values `source` and `target`, the following code yields `#!cpp true`:
+For two JSON values `source` and `target`, the following code always yields `#!cpp true`:
 ```cpp
 source.patch(diff(source, target)) == target;
 ```
 
-The equality holds up to [`operator==`](operator_eq.md), so it has the following exceptions:
-
-- A value that is not equal to itself cannot round-trip. This applies to `NaN` (also nested in an array or object) and
-  to [discarded](is_discarded.md) values: `diff` emits a `replace` operation for them. A `NaN` in the patch is
-  serialized as `#!json null`, so a patch that was dumped and parsed again would set `#!json null`.
-- Numbers that compare equal produce no operation, even if their types differ or if one is zero and the other is
-  negative zero: `diff(1, 1.0)` (integer and floating-point), `diff(1u, 1)` (unsigned and signed integer) and
-  `diff(0.0, -0.0)` (positive and negative zero) all return `#!json []`. The patched value is then the `source` and
-  keeps its number type and sign.
-
 ## Parameters
 
 `source` (in)
@@ -32,12 +21,6 @@ The equality holds up to [`operator==`](operator_eq.md), so it has the following
 `target` (in)
 :   JSON value to compare against
 
-`path` (in)
-:   a prefix that is put verbatim in front of the `path` member of every operation (default: `""`, which addresses the
-    root of the value). The prefix is neither escaped nor validated: `#!cpp diff(1, 2, "abc")` yields an operation with
-    the `path` `abc`, which is not a valid JSON Pointer. Use it with a valid JSON Pointer such as `/root` and escape
-    `~` and `/` in its reference tokens (see [JSON Pointer](../../features/json_pointer.md)).
-
 ## Return value
 
 a JSON patch to convert the `source` to `target`
@@ -48,32 +31,11 @@ Strong guarantee: `source` and `target` are never modified.
 
 ## Complexity
 
-Linear in the total number of values (including nested ones) in `source` and `target`, times the cost of a key-based
+Linear in the lengths of `source` and `target`.
-object operation (looking up a key in an object): logarithmic for [`json`](../json.md), and linear for
-[`ordered_json`](../ordered_json.md) (see [`ordered_map` complexity](../ordered_map.md#complexity)). For
-`ordered_json`, diffing two objects with `n` and `m` members therefore takes O((n+m)²) when their keys do not line up
-(e.g., a key was added or the keys are in a different order). The size of the patch is proportional to the number of
-operations times the length of their paths, so a small change deep inside a value yields a long `path`.
 
 ## Notes
 
-- Currently, only `remove`, `add`, and `replace` operations are generated.
+Currently, only `remove`, `add`, and `replace` operations are generated.
-- The patch is correct, but not guaranteed to be minimal. For instance, `diff([1,2,3], [0,1,2,3])` yields three
-  `replace` operations and one `add` operation instead of a single insertion.
-- Differences between two arrays are reported index by index. Elements that were added at the end of the array are added
-  with `add` operations on the path `/-` (appended in order), and elements that were removed are removed with `remove`
-  operations from the highest index down to the lowest, so that the remaining indices stay valid.
-- For objects, the operations for the members of `source` come first (`replace`, `remove`, or the operations for nested
-  values, in the iteration order of `source`), followed by `add` operations for the members that only `target` has.
-- For [`ordered_json`](../ordered_json.md), objects with the same keys in a different order are different. As a patch
-  cannot reorder members, `diff` removes all keys of the `source` object and adds them again in the order of the
-  `target`.
-- If `source` and `target` differ as a whole (e.g., different types), the patch consists of a single `replace`
-  operation for the root of the value, i.e., with the `path` `""` (or the given `path` prefix).
-- The `value` members of the patch hold copies of values of `target`. A [binary](../../features/binary_values.md) value
-  has no JSON representation: when a patch that contains one is serialized, it becomes an object such as
-  `#!json {"bytes":[1,3],"subtype":null}`, so a parsed patch no longer holds a binary value (and would set that object
-  instead).
           
 ## Examples
 
@@ -93,12 +55,11 @@ operations times the length of their paths, so a small change deep inside a valu
 
 ## See also
 
-- [RFC 6902 (JSON Patch)](https://tools.ietf.org/html/rfc6902) - specification of JSON Patch
+- [RFC 6902 (JSON Patch)](https://tools.ietf.org/html/rfc6902)
-- [`patch`](patch.md) - applies a JSON Patch
+- [patch](patch.md) applies a JSON Patch
-- [`patch_inplace`](patch_inplace.md) - applies a JSON Patch in place
+- [patch_inplace](patch_inplace.md) applies a JSON Patch in place
-- [`merge_patch`](merge_patch.md) - applies a JSON Merge Patch
+- [merge_patch](merge_patch.md) applies a JSON Merge Patch
-- [`merge_diff`](merge_diff.md) - creates a diff as a JSON Merge Patch
+- [merge_diff](merge_diff.md) creates a diff as a JSON Merge Patch
-- [JSON Patch and Diff](../../features/json_patch.md) - the article on JSON Patch
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/dump.md

@@ -89,9 +89,9 @@ Binary values are serialized as an object containing two keys:
 
 ## See also
 
-- [`to_string`](to_string.md) - returns a string representation of a JSON value
+- [to_string](to_string.md) returns a string representation of a JSON value
-- [`operator<<`](../operator_ltlt.md) - serialize to stream
+- [operator<<](../operator_ltlt.md) serialize to stream
-- [`basic_json_view::dump`](../basic_json_view/dump.md) - the corresponding function of `basic_json_view`, serializing
+- [`basic_json_view::dump`](../basic_json_view/dump.md) the corresponding function of `basic_json_view`, serializing
   directly from a flat index without building a `basic_json` value
 - [Serialization](../../features/serialization.md) - the serialization article
 

docs/mkdocs/docs/api/basic_json/emplace.md

@@ -63,8 +63,8 @@ Logarithmic in the size of the container, O(log(`size()`)).
 
 ## See also
 
-- [`emplace_back`](emplace_back.md) - add a value to an array
+- [emplace_back](emplace_back.md) add a value to an array
-- [`insert`](insert.md) - add values to an array/object
+- [insert](insert.md) add values to an array/object
 - [Modifying values](../../features/modifying_values.md) - the article on modifying values
 
 ## Version history

docs/mkdocs/docs/api/basic_json/emplace_back.md

@@ -61,8 +61,8 @@ Amortized constant.
 
 ## See also
 
-- [`operator+=`](operator+=.md) - add a value to an array/object
+- [operator+=](operator+=.md) add a value to an array/object
-- [`push_back`](push_back.md) - add a value to an array/object
+- [push_back](push_back.md) add a value to an array/object
 - [Modifying values](../../features/modifying_values.md) - the article on modifying values
 
 ## Version history

docs/mkdocs/docs/api/basic_json/empty.md

@@ -41,7 +41,7 @@ bool empty() const noexcept
 
 ## Notes
 
-This function does not return whether a string stored as JSON value is empty — it returns whether the JSON container
+This function does not return whether a string stored as JSON value is empty -- it returns whether the JSON container
 itself is empty which is `#!cpp false` in the case of a string.
 
 ## Examples
@@ -62,9 +62,9 @@ itself is empty which is `#!cpp false` in the case of a string.
 
 ## See also
 
-- [`size`](size.md) - returns the number of elements
+- [size](size.md) returns the number of elements
-- [`clear`](clear.md) - clears the content and resets the value to the default value
+- [clear](clear.md) clears the content and resets the value to the default value
-- [`basic_json_view::empty`](../basic_json_view/empty.md) - the same check on a zero-copy view
+- [basic_json_view::empty](../basic_json_view/empty.md) - the same check on a zero-copy view
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/end.md

@@ -7,12 +7,7 @@ const_iterator end() const noexcept;
 
 Returns an iterator to one past the last element.
 
-<div class="nj-fig-wrap" markdown>
+![Illustration from cppreference.com](../../images/range-begin-end.svg)
---8<-- "images/range-begin-end.svg"
-</div>
-
-<p class="nj-caption" markdown>`end()` points to the position after the last element and `begin()` to the first element;
-the dashed cell is the past-the-last position, which must not be dereferenced.</p>
 
 ## Return value
 
@@ -44,11 +39,11 @@ Constant.
 
 ## See also
 
-- [`begin`](begin.md) - returns an iterator to the first element
+- [begin](begin.md) returns an iterator to the first element
-- [`cend`](cend.md) - returns a const iterator to one past the last 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
+- [rend](rend.md) returns a reverse iterator to one before the first element
 - [Iterators](../../features/iterators.md) - the article on iterators
-- [`basic_json_view::end`](../basic_json_view/end.md) - the same iteration on a zero-copy view
+- [basic_json_view::end](../basic_json_view/end.md) - the same iteration on a zero-copy view
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/end_pos.md

@@ -60,9 +60,8 @@ Constant.
 
 ## See also
 
-- [`start_pos`](start_pos.md) - to access the start position
+- [start_pos](start_pos.md) to access the start position
-- [`JSON_DIAGNOSTIC_POSITIONS`](../macros/json_diagnostic_positions.md) - overview of the supported conversions
+- [JSON_DIAGNOSTIC_POSITIONS](../macros/json_diagnostic_positions.md) for an overview of the diagnostic positions
-- [Parsing and Exceptions](../../features/parsing/parse_exceptions.md) - handling parse errors and locating them in the input
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/erase.md

@@ -204,8 +204,8 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
 ## See also
 
-- [`clear`](clear.md) - clears the contents
+- [clear](clear.md) clears the contents
-- [`insert`](insert.md) - add values to an array/object
+- [insert](insert.md) add values to an array/object
 - [Modifying values](../../features/modifying_values.md) - the article on modifying values
 
 ## Version history

docs/mkdocs/docs/api/basic_json/error_handler_t.md

@@ -61,7 +61,7 @@ keep
 
 ## See also
 
-- [`dump`](dump.md) - serializes a JSON value, with an `error_handler_t` parameter to configure invalid UTF-8 handling
+- [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

docs/mkdocs/docs/api/basic_json/exception.md

@@ -40,9 +40,6 @@ classDiagram
     style json_exception fill:#CCCCFF
 ```
 
-<p class="nj-caption" markdown>Class hierarchy of the library's exceptions; arrows point from a derived class to its
-base class, and the highlighted box is `basic_json::exception`.</p>
-
 Subclasses:
 
 - [`parse_error`](parse_error.md) for exceptions indicating a parse error
@@ -83,11 +80,7 @@ constructor.
 
 ## See also
 
-- [List of exceptions](../../home/exceptions.md) - overview of all exceptions thrown by the library
+[List of exceptions](../../home/exceptions.md)
-- [Working Without Exceptions](../../features/no_exceptions.md) - using the library without exceptions
-- [`JSON_DIAGNOSTICS`](../macros/json_diagnostics.md) - extended exception messages with the path of the failing value
-- [Parsing and Exceptions](../../features/parsing/parse_exceptions.md) - parsing alternatives that do not throw
-- [Debugging](../../home/debugging.md) - debugging aids
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/find.md

@@ -91,11 +91,10 @@ Logarithmic in the size of the JSON object.
 
 ## See also
 
-- [`count`](count.md) - returns the number of occurrences of a key
+- [count](count.md) returns the number of occurrences of a key
-- [`contains`](contains.md) - checks whether a key exists
+- [contains](contains.md) checks whether a key exists
-- [`basic_json_view::find`](../basic_json_view/find.md) - the same lookup on a zero-copy view (a duplicate key resolves
+- [basic_json_view::find](../basic_json_view/find.md) - the same lookup on a zero-copy view (a duplicate key resolves
   to the first member, whereas `parse()` keeps the last)
-- [Element Access](../../features/element_access/index.md#does-this-key-exist) - how to test whether a key exists
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/flatten.md

@@ -58,8 +58,7 @@ Empty objects and arrays are flattened to `#!json null` and will not be reconstr
 
 ## See also
 
-- [`unflatten`](unflatten.md) - the reverse function
+- [unflatten](unflatten.md) the reverse function
-- [JSON Pointer](../../features/json_pointer.md#flatten-unflatten) - the article on JSON Pointer and flattening
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/format_as.md

@@ -86,8 +86,8 @@ std::string format_as(const BasicJsonType& j)
 
 ## See also
 
-- [`dump`](dump.md) - serialize a JSON value to a string
+- [dump](dump.md)
-- [`std::formatter<basic_json>`](std_formatter.md) - the `std::format` (C++20) equivalent
+- [std::formatter<basic_json>](std_formatter.md) - the `std::format` (C++20) equivalent
 - [Serialization](../../features/serialization.md) - the serialization article
 
 ## Version history

docs/mkdocs/docs/api/basic_json/from_bjdata.md

@@ -82,11 +82,8 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - 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, or if a string value or object key is not valid UTF-8 and `error_handler` is `strict`
-- Throws [parse_error.115](../../home/exceptions.md#jsonexceptionparse_error115) if the text of a high-precision
-  number (`H`) is not a valid number
 - Throws [out_of_range.408](../../home/exceptions.md#jsonexceptionout_of_range408) if the size of an optimized container
-  cannot be represented by `std::size_t` or exceeds the container's `max_size()`, or if the product of the dimensions of
+  or n-dimensional array cannot be represented by `std::size_t`
-  an n-dimensional array overflows
 
 ## Complexity
 
@@ -110,16 +107,12 @@ Linear in the size of the input.
 
 ## See also
 
-- [BJData](../../features/binary_formats/bjdata.md) - the format, its byte layout and how values are mapped
+- [to_bjdata](to_bjdata.md) create a BJData serialization of a JSON value
-- [Binary formats](../../features/binary_formats/index.md) - overview and comparison of the supported binary formats
+- [from_cbor](from_cbor.md) create a JSON value from an input in CBOR format
-- [Parsing untrusted input](../../features/parsing/untrusted_input.md) - limits and safe handling of hostile data
+- [from_msgpack](from_msgpack.md) create a JSON value from an input in MessagePack format
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [from_bson](from_bson.md) create a JSON value from an input in BSON format
-- [`to_bjdata`](to_bjdata.md) - create a BJData serialization of a JSON value
+- [from_ubjson](from_ubjson.md) create a JSON value from an input in UBJSON format
-- [`from_cbor`](from_cbor.md) - create a JSON value from an input in CBOR format
+- [from_bon8](from_bon8.md) create a JSON value from an input in BON8 format
-- [`from_msgpack`](from_msgpack.md) - create a JSON value from an input in MessagePack format
-- [`from_bson`](from_bson.md) - create a JSON value from an input in BSON format
-- [`from_ubjson`](from_ubjson.md) - create a JSON value from an input in UBJSON format
-- [`from_bon8`](from_bon8.md) - create a JSON value from an input in BON8 format
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/from_bon8.md

@@ -74,11 +74,6 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if a parse error occurs, for instance
   an invalid byte, a string that is not valid UTF-8, or an object key that is not a string
 
-The UTF-8 validity of strings is always checked, independent of
-[`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md), because the end of a BON8 string is determined from
-its encoding. Duplicate object keys are accepted; the last value wins (see
-[BON8](../../features/binary_formats/bon8.md)).
-
 ## Complexity
 
 Linear in the size of the input.
@@ -101,15 +96,12 @@ Linear in the size of the input.
 
 ## See also
 
-- [BON8](../../features/binary_formats/bon8.md) - the format, its byte layout and how values are mapped
+- [to_bon8](to_bon8.md) create a BON8 serialization of a JSON value
-- [Binary formats](../../features/binary_formats/index.md) - overview and comparison of the supported binary formats
+- [from_cbor](from_cbor.md) create a JSON value from an input in CBOR format
-- [Parsing untrusted input](../../features/parsing/untrusted_input.md) - limits and safe handling of hostile data
+- [from_msgpack](from_msgpack.md) create a JSON value from an input in MessagePack format
-- [`to_bon8`](to_bon8.md) - create a BON8 serialization of a JSON value
+- [from_bson](from_bson.md) create a JSON value from an input in BSON format
-- [`from_cbor`](from_cbor.md) - create a JSON value from an input in CBOR format
+- [from_ubjson](from_ubjson.md) create a JSON value from an input in UBJSON format
-- [`from_msgpack`](from_msgpack.md) - create a JSON value from an input in MessagePack format
+- [from_bjdata](from_bjdata.md) create a JSON value from an input in BJData format
-- [`from_bson`](from_bson.md) - create a JSON value from an input in BSON format
-- [`from_ubjson`](from_ubjson.md) - create a JSON value from an input in UBJSON format
-- [`from_bjdata`](from_bjdata.md) - create a JSON value from an input in BJData format
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/from_bson.md

@@ -80,8 +80,7 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [`parse_error.110`](../../home/exceptions.md#jsonexceptionparse_error110) if the given input ends prematurely or
   the end of the input was not reached when `strict` was set to true
 - Throws [`parse_error.112`](../../home/exceptions.md#jsonexceptionparse_error112) if a parse error occurs (e.g., an
-  invalid string or byte array length, an invalid inner length of a binary value with subtype `0x02`, or a document size
+  invalid string or byte array length)
-  that does not match the content; `strict` does not affect the document size checks)
 - 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
@@ -109,17 +108,13 @@ Linear in the size of the input.
 
 ## See also
 
-- [BSON](../../features/binary_formats/bson.md) - the format, its byte layout and how values are mapped
+- [BSON specification](http://bsonspec.org/spec.html)
-- [Binary formats](../../features/binary_formats/index.md) - overview and comparison of the supported binary formats
+- [to_bson](to_bson.md) for the analogous serialization
-- [Parsing untrusted input](../../features/parsing/untrusted_input.md) - limits and safe handling of hostile data
+- [from_cbor](from_cbor.md) for the related CBOR format
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [from_msgpack](from_msgpack.md) for the related MessagePack format
-- [BSON specification](http://bsonspec.org/spec.html) - specification of the BSON format
+- [from_ubjson](from_ubjson.md) for the related UBJSON format
-- [`to_bson`](to_bson.md) - the analogous serialization
+- [from_bjdata](from_bjdata.md) for the related BJData format
-- [`from_cbor`](from_cbor.md) - the related CBOR format
+- [from_bon8](from_bon8.md) for the related BON8 format
-- [`from_msgpack`](from_msgpack.md) - the related MessagePack format
-- [`from_ubjson`](from_ubjson.md) - the related UBJSON format
-- [`from_bjdata`](from_bjdata.md) - the related BJData format
-- [`from_bon8`](from_bon8.md) - the related BON8 format
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/from_cbor.md

@@ -32,10 +32,8 @@ The exact mapping and its limitations are described on a [dedicated page](../../
     
     - an `std::istream` object
     - a `FILE` pointer
-    - a C-style array of characters (its terminating NUL is read as trailing data: `parse_error.110` unless `strict` is
+    - a C-style array of characters
-      `false`)
+    - a pointer to a null-terminated string of single byte characters
-    - a pointer to a null-terminated string of single byte characters (read up to the first 0x00 byte, which is a valid
-      CBOR byte)
     - a container `obj` for which `begin(obj)` and `end(obj)` produce a valid pair of iterators
       (as found via ADL or member functions, with semantics compatible to `std::begin` and `std::end`)
 
@@ -91,14 +89,8 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - 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), if the head of a string or byte string is
+  other types are not supported, as JSON object keys are always strings), or if a string value or object key is not
-  malformed (including a chunk of the wrong type or an indefinite-length string nested inside an indefinite-length
+  valid UTF-8 and `error_handler` is `strict`
-  string), or if a string value or object key (or one chunk of an indefinite-length string) is not valid UTF-8 and
-  `error_handler` is `strict`
-- Throws [out_of_range.408](../../home/exceptions.md#jsonexceptionout_of_range408) if an array or map announces
-  a length that `std::size_t` cannot hold, or that equals `std::size_t(-1)` (for example `9B FF FF FF FF FF FF FF FF`)
-- Throws [out_of_range.406](../../home/exceptions.md#jsonexceptionout_of_range406) if a floating-point number does not
-  fit into `number_float_t`
 
 ## Complexity
 
@@ -122,16 +114,12 @@ Linear in the size of the input.
 
 ## See also
 
-- [CBOR](../../features/binary_formats/cbor.md) - the format, its byte layout and how values are mapped
+- [to_cbor](to_cbor.md) create a CBOR serialization of a JSON value
-- [Binary formats](../../features/binary_formats/index.md) - overview and comparison of the supported binary formats
+- [from_msgpack](from_msgpack.md) create a JSON value from an input in MessagePack format
-- [Parsing untrusted input](../../features/parsing/untrusted_input.md) - limits and safe handling of hostile data
+- [from_bson](from_bson.md) create a JSON value from an input in BSON format
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [from_ubjson](from_ubjson.md) create a JSON value from an input in UBJSON format
-- [`to_cbor`](to_cbor.md) - create a CBOR serialization of a JSON value
+- [from_bjdata](from_bjdata.md) create a JSON value from an input in BJData format
-- [`from_msgpack`](from_msgpack.md) - create a JSON value from an input in MessagePack format
+- [from_bon8](from_bon8.md) create a JSON value from an input in BON8 format
-- [`from_bson`](from_bson.md) - create a JSON value from an input in BSON format
-- [`from_ubjson`](from_ubjson.md) - create a JSON value from an input in UBJSON format
-- [`from_bjdata`](from_bjdata.md) - create a JSON value from an input in BJData format
-- [`from_bon8`](from_bon8.md) - create a JSON value from an input in BON8 format
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/from_msgpack.md

@@ -107,16 +107,12 @@ Linear in the size of the input.
 
 ## See also
 
-- [MessagePack](../../features/binary_formats/messagepack.md) - the format, its byte layout and how values are mapped
+- [to_msgpack](to_msgpack.md) create a MessagePack serialization of a JSON value
-- [Binary formats](../../features/binary_formats/index.md) - overview and comparison of the supported binary formats
+- [from_cbor](from_cbor.md) create a JSON value from an input in CBOR format
-- [Parsing untrusted input](../../features/parsing/untrusted_input.md) - limits and safe handling of hostile data
+- [from_bson](from_bson.md) create a JSON value from an input in BSON format
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [from_ubjson](from_ubjson.md) create a JSON value from an input in UBJSON format
-- [`to_msgpack`](to_msgpack.md) - create a MessagePack serialization of a JSON value
+- [from_bjdata](from_bjdata.md) create a JSON value from an input in BJData format
-- [`from_cbor`](from_cbor.md) - create a JSON value from an input in CBOR format
+- [from_bon8](from_bon8.md) create a JSON value from an input in BON8 format
-- [`from_bson`](from_bson.md) - create a JSON value from an input in BSON format
-- [`from_ubjson`](from_ubjson.md) - create a JSON value from an input in UBJSON format
-- [`from_bjdata`](from_bjdata.md) - create a JSON value from an input in BJData format
-- [`from_bon8`](from_bon8.md) - create a JSON value from an input in BON8 format
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/from_ubjson.md

@@ -79,18 +79,11 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 
 - Throws [parse_error.110](../../home/exceptions.md#jsonexceptionparse_error110) if the given input ends prematurely or
   the end of the file was not reached when `strict` was set to true
-- Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if an invalid type marker is read
+- Throws [parse_error.112](../../home/exceptions.md#jsonexceptionparse_error112) if a parse error occurs
-  (including a type marker after `$` of an optimized container, even if its count is 0), or if `$` is not followed by `#`
 - Throws [parse_error.113](../../home/exceptions.md#jsonexceptionparse_error113) if a string could not be parsed
-  successfully (negative or non-integer length, `C` followed by a byte above 0x7F), if the count of an optimized
+  successfully, or if a string value or object key is not valid UTF-8 and `error_handler` is `strict`
-  container is negative, 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
-- Throws [parse_error.115](../../home/exceptions.md#jsonexceptionparse_error115) if the text of a high-precision number
+  or n-dimensional array cannot be represented by `std::size_t`
-  (`H`) is not a valid JSON number
-- Throws [out_of_range.406](../../home/exceptions.md#jsonexceptionout_of_range406) if a high-precision number, or a
-  float64 when `number_float_t` is `float`, does not fit into `number_float_t`
-- Throws [out_of_range.408](../../home/exceptions.md#jsonexceptionout_of_range408) if the count of an optimized
-  container exceeds the capacity of the container (or of `std::size_t`), or if an optimized array of `Z`, `T`, or `F` has
-  more than 1,048,576 elements
 
 ## Complexity
 
@@ -114,16 +107,12 @@ Linear in the size of the input.
 
 ## See also
 
-- [UBJSON](../../features/binary_formats/ubjson.md) - the format, its byte layout and how values are mapped
+- [to_ubjson](to_ubjson.md) create a UBJSON serialization of a JSON value
-- [Binary formats](../../features/binary_formats/index.md) - overview and comparison of the supported binary formats
+- [from_cbor](from_cbor.md) create a JSON value from an input in CBOR format
-- [Parsing untrusted input](../../features/parsing/untrusted_input.md) - limits and safe handling of hostile data
+- [from_msgpack](from_msgpack.md) create a JSON value from an input in MessagePack format
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [from_bson](from_bson.md) create a JSON value from an input in BSON format
-- [`to_ubjson`](to_ubjson.md) - create a UBJSON serialization of a JSON value
+- [from_bjdata](from_bjdata.md) create a JSON value from an input in BJData format
-- [`from_cbor`](from_cbor.md) - create a JSON value from an input in CBOR format
+- [from_bon8](from_bon8.md) create a JSON value from an input in BON8 format
-- [`from_msgpack`](from_msgpack.md) - create a JSON value from an input in MessagePack format
-- [`from_bson`](from_bson.md) - create a JSON value from an input in BSON format
-- [`from_bjdata`](from_bjdata.md) - create a JSON value from an input in BJData format
-- [`from_bon8`](from_bon8.md) - create a JSON value from an input in BON8 format
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/front.md

@@ -50,10 +50,9 @@ Constant.
 
 ## See also
 
-- [`back`](back.md) - to access the last element
+- [back](back.md) to access the last element
-- [`basic_json_view::front`](../basic_json_view/front.md) - the same access on a zero-copy view (document order, not
+- [basic_json_view::front](../basic_json_view/front.md) - the same access on a zero-copy view (document order, not
   sorted; duplicate keys are visited)
-- [Element Access](../../features/element_access/index.md) - overview of all ways to access elements
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/get.md

@@ -178,14 +178,13 @@ overload (3).
 
 ## See also
 
-- [`get_to`](get_to.md) - convert and write into a passed value
+- [get_to](get_to.md) convert and write into a passed value
-- [`get_ptr`](get_ptr.md) - get a pointer to the stored value
+- [get_ptr](get_ptr.md) get a pointer to the stored value
-- [`get_ref`](get_ref.md) - get a reference to the stored value
+- [get_ref](get_ref.md) get a reference to the stored value
-- [`operator ValueType`](operator_ValueType.md) - get a value via implicit conversion
+- [operator ValueType](operator_ValueType.md) get a value via implicit conversion
 - [Converting values](../../features/conversions.md) - the type conversions article
-- [`basic_json_view::get`](../basic_json_view/get.md) - the same conversion on a zero-copy view (many types are
+- [basic_json_view::get](../basic_json_view/get.md) - the same conversion on a zero-copy view (many types are
   converted without ever building a `basic_json` value)
-- [Arbitrary Type Conversions](../../features/arbitrary_types.md) - make your own types usable with `get`
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/get_allocator.md

@@ -36,7 +36,7 @@ Constant.
 
 ## See also
 
-- [`basic_json`](index.md#template-parameters) - the class template, with `AllocatorType` as one of its template parameters
+- [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

docs/mkdocs/docs/api/basic_json/get_binary.md

@@ -42,11 +42,8 @@ Constant.
 
 ## See also
 
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [get](get.md) get a value (explicit conversion)
-- [`binary`](binary.md) - create a binary value
+- [get_ref](get_ref.md) get a reference to the stored value
-- [`is_binary`](is_binary.md) - check whether a value is binary
-- [`get`](get.md) - get a value (explicit conversion)
-- [`get_ref`](get_ref.md) - get a reference to the stored value
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/get_ptr.md

@@ -86,8 +86,7 @@ Constant.
 
 ## See also
 
-- [`get_ref()`](get_ref.md) - get a reference value
+- [get_ref()](get_ref.md) get a reference value
-- [Converting values](../../features/conversions.md) - getting values out, with or without copying
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/get_ref.md

@@ -60,10 +60,9 @@ Constant.
 
 ## See also
 
-- [`get_ptr()`](get_ptr.md) - get a pointer value
+- [get_ptr()](get_ptr.md) get a pointer value
-- [`basic_json_view::get_string`](../basic_json_view/get_string.md) - the closest counterpart on a zero-copy view: a
+- [basic_json_view::get_string](../basic_json_view/get_string.md) - the closest counterpart on a zero-copy view: a
   string without a copy, but as a view rather than a reference to a value that must already exist
-- [Converting values](../../features/conversions.md) - getting values out, with or without copying
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/get_to.md

@@ -68,12 +68,11 @@ Depends on the `json_serializer<ValueType>::from_json()` implementation.
 
 ## See also
 
-- [`get`](get.md) - get a value (explicit conversion)
+- [get](get.md) get a value (explicit conversion)
-- [`get_ref`](get_ref.md) - get a reference to the stored value
+- [get_ref](get_ref.md) get a reference to the stored value
-- [`get_ptr`](get_ptr.md) - get a pointer to the stored value
+- [get_ptr](get_ptr.md) get a pointer to the stored value
 - [Converting values](../../features/conversions.md) - the type conversions article
-- [`basic_json_view::get_to`](../basic_json_view/get_to.md) - the same conversion on a zero-copy view
+- [basic_json_view::get_to](../basic_json_view/get_to.md) - the same conversion on a zero-copy view
-- [Arbitrary Type Conversions](../../features/arbitrary_types.md) - make your own types usable with `get_to`
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/index.md

@@ -121,7 +121,6 @@ The class satisfies the following concept requirements:
 - [**json_pointer**](../json_pointer/index.md) - JSON Pointer implementation
 - [**json_serializer**](json_serializer.md) - type of the serializer to for conversions from/to JSON
 - [**error_handler_t**](error_handler_t.md) - type to choose behavior on decoding errors
-- [**bjdata_version_t**](bjdata_version_t.md) - type to choose the BJData version to write
 - [**cbor_tag_handler_t**](cbor_tag_handler_t.md) - type to choose how to handle CBOR tags
 - **initializer_list_t** - type for initializer lists of `basic_json` values
 - [**input_format_t**](input_format_t.md) - type to choose the format to parse
@@ -189,7 +188,7 @@ The class satisfies the following concept requirements:
 Functions to inspect the type of a JSON value.
 
 - [**type**](type.md) - return the type of the JSON value
-- [`operator value_t`](operator_value_t.md) - return the type of the JSON value
+- [**operator value_t**](operator_value_t.md) - return the type of the JSON value
 - [**type_name**](type_name.md) - return the type as string
 - [**is_primitive**](is_primitive.md) - return whether the type is primitive
 - [**is_structured**](is_structured.md) - return whether the type is structured
@@ -218,7 +217,7 @@ Direct access to the stored value of a JSON value.
 - [**get_to**](get_to.md) - get a value and write it to a destination
 - [**get_ptr**](get_ptr.md) - get a pointer value
 - [**get_ref**](get_ref.md) - get a reference value
-- [`operator ValueType`](operator_ValueType.md) - get a 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
 
@@ -359,15 +358,10 @@ Access to the JSON value
 
 ## See also
 
-- [RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format](https://tools.ietf.org/html/rfc8259) -
+- [RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format](https://tools.ietf.org/html/rfc8259)
-  specification of the JSON data interchange format
+- [basic_json_document](../basic_json_document/index.md) / [basic_json_view](../basic_json_view/index.md) - parse a JSON
-- [`basic_json_document`](../basic_json_document/index.md) - / [`basic_json_view`](../basic_json_view/index.md) - parse a JSON
   text into a flat index and read it through a view
 - [Zero-copy JSON views](../../features/json_view.md) - when to use a document and a view instead of a `basic_json`
-- [Types](../../features/types/index.md) - how JSON values are stored and which types exist
-- [Converting values](../../features/conversions.md) - get values out of a JSON value and put values in
-- [Creating JSON values](../../features/creating_values.md) - all the ways to build a JSON value
-- [Arbitrary Type Conversions](../../features/arbitrary_types.md) - convert your own types to and from JSON
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/input_format_t.md

@@ -53,9 +53,8 @@ bon8
 
 ## See also
 
-- [`sax_parse`](sax_parse.md) - generic SAX parse interface, taking an `input_format_t` to select the input format
+- [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
+- [cbor_tag_handler_t](cbor_tag_handler_t.md) configures how CBOR tags are treated while parsing
-- [Binary Formats](../../features/binary_formats/index.md) - CBOR, MessagePack, BSON, and other formats
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/insert.md

@@ -185,11 +185,10 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
 ## See also
 
-- [`emplace`](emplace.md) - add a value to an object
+- [emplace](emplace.md) add a value to an object
-- [`emplace_back`](emplace_back.md) - add a value to an array
+- [emplace_back](emplace_back.md) add a value to an array
-- [`push_back`](push_back.md) - add a value to an array/object
+- [push_back](push_back.md) add a value to an array/object
-- [`update`](update.md) - merges objects
+- [update](update.md) merges objects
-- [Modifying values](../../features/modifying_values.md) - the article on modifying values
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/invalid_iterator.md

@@ -40,9 +40,6 @@ classDiagram
     style json_invalid_iterator fill:#CCCCFF
 ```
 
-<p class="nj-caption" markdown>Class hierarchy of the library's exceptions; arrows point from a derived class to its
-base class, and the highlighted box is `basic_json::invalid_iterator`.</p>
-
 ## Member functions
 
 - **what** - returns explanatory string
@@ -69,14 +66,12 @@ base class, and the highlighted box is `basic_json::invalid_iterator`.</p>
 
 ## See also
 
-- [`exception`](exception.md) - the base class of all exceptions thrown by the library
+- [`exception`](exception.md) for the base class of all exceptions thrown by the library
-- [List of iterator errors](../../home/exceptions.md#iterator-errors) - overview of iterator errors (`invalid_iterator`)
+- [List of iterator errors](../../home/exceptions.md#iterator-errors)
-- [`parse_error`](parse_error.md) - exceptions indicating a parse error
+- [`parse_error`](parse_error.md) for exceptions indicating a parse error
-- [`type_error`](type_error.md) - exceptions indicating executing a member function with a wrong type
+- [`type_error`](type_error.md) for exceptions indicating executing a member function with a wrong type
-- [`out_of_range`](out_of_range.md) - exceptions indicating access out of the defined range
+- [`out_of_range`](out_of_range.md) for exceptions indicating access out of the defined range
-- [`other_error`](other_error.md) - exceptions indicating other library errors
+- [`other_error`](other_error.md) for exceptions indicating other library errors
-- [Exceptions](../../home/exceptions.md) - all exceptions and their error codes
-- [`JSON_DIAGNOSTICS`](../macros/json_diagnostics.md) - extended exception messages with the path of the failing value
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_array.md

@@ -36,12 +36,11 @@ Constant.
 
 ## See also
 
-- [`is_object`](is_object.md) - checks whether the JSON value is an object
+- [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)
+- [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
+- [type](type.md) returns the type of the JSON value
-- [`array_t`](array_t.md) - the type used to store JSON arrays
+- [array_t](array_t.md) the type used to store JSON arrays
-- [`basic_json_view::is_array`](../basic_json_view/is_array.md) - the same check on a zero-copy view
+- [basic_json_view::is_array](../basic_json_view/is_array.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_binary.md

@@ -36,11 +36,10 @@ Constant.
 
 ## See also
 
-- [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
+- [is_primitive](is_primitive.md) checks whether the JSON value is primitive
-- [`is_primitive`](is_primitive.md) - checks whether the JSON value is primitive
+- [binary_t](binary_t.md) the type used to store binary values
-- [`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
-- [`get_binary`](get_binary.md) - returns a reference to the stored binary value
+- [basic_json_view::is_binary](../basic_json_view/is_binary.md) - the same check on a zero-copy view
-- [`basic_json_view::is_binary`](../basic_json_view/is_binary.md) - the same check on a zero-copy view
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_boolean.md

@@ -36,10 +36,9 @@ Constant.
 
 ## See also
 
-- [`boolean_t`](boolean_t.md) - the type used to store JSON booleans
+- [boolean_t](boolean_t.md) the type used to store JSON booleans
-- [`is_primitive`](is_primitive.md) - checks whether the JSON value is primitive
+- [is_primitive](is_primitive.md) checks whether the JSON value is primitive
-- [`basic_json_view::is_boolean`](../basic_json_view/is_boolean.md) - the same check on a zero-copy view
+- [basic_json_view::is_boolean](../basic_json_view/is_boolean.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_discarded.md

@@ -87,9 +87,8 @@ with `allow_exceptions` set to `#!cpp false`: a parse error then yields a discar
 
 ## See also
 
-- [`basic_json_view::is_discarded`](../basic_json_view/is_discarded.md) - the corresponding check on a zero-copy view,
+- [basic_json_view::is_discarded](../basic_json_view/is_discarded.md) - the corresponding check on a zero-copy view,
   which is `#!cpp true` if the view refers to no value
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_null.md

@@ -36,12 +36,11 @@ Constant.
 
 ## See also
 
-- [`is_array`](is_array.md) - checks whether the JSON value is an array
+- [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
+- [is_object](is_object.md) checks whether the JSON value is an object
-- [`type`](type.md) - returns the type of the JSON value
+- [type](type.md) returns the type of the JSON value
-- [`value_t`](value_t.md) - the enumeration of JSON types
+- [value_t](value_t.md) the enumeration of JSON types
-- [`basic_json_view::is_null`](../basic_json_view/is_null.md) - the same check on a zero-copy view
+- [basic_json_view::is_null](../basic_json_view/is_null.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_number.md

@@ -46,12 +46,10 @@ constexpr bool is_number() const noexcept
 
 ## See also
 
-- [`is_number_integer()`](is_number_integer.md) - check if the value is an integer or unsigned integer number
+- [is_number_integer()](is_number_integer.md) check if the value is an integer or unsigned integer number
-- [`is_number_unsigned()`](is_number_unsigned.md) - check if the value is an unsigned integer number
+- [is_number_unsigned()](is_number_unsigned.md) check if the value is an unsigned integer number
-- [`is_number_float()`](is_number_float.md) - check if the value is a floating-point number
+- [is_number_float()](is_number_float.md) check if the value is a floating-point number
-- [`basic_json_view::is_number`](../basic_json_view/is_number.md) - the same check on a zero-copy view
+- [basic_json_view::is_number](../basic_json_view/is_number.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
-- [Number Handling](../../features/types/number_handling.md) - how numbers are stored and converted
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_number_float.md

@@ -37,12 +37,10 @@ Constant.
 
 ## See also
 
-- [`is_number()`](is_number.md) - check if the value is a number
+- [is_number()](is_number.md) check if the value is a number
-- [`is_number_integer()`](is_number_integer.md) - check if the value is an integer or unsigned integer number
+- [is_number_integer()](is_number_integer.md) check if the value is an integer or unsigned integer number
-- [`is_number_unsigned()`](is_number_unsigned.md) - check if the value is an unsigned integer number
+- [is_number_unsigned()](is_number_unsigned.md) check if the value is an unsigned integer number
-- [`basic_json_view::is_number_float`](../basic_json_view/is_number_float.md) - the same check on a zero-copy view
+- [basic_json_view::is_number_float](../basic_json_view/is_number_float.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
-- [Number Handling](../../features/types/number_handling.md) - how numbers are stored and converted
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_number_integer.md

@@ -37,12 +37,10 @@ Constant.
 
 ## See also
 
-- [`is_number()`](is_number.md) - check if the value is a number
+- [is_number()](is_number.md) check if the value is a number
-- [`is_number_unsigned()`](is_number_unsigned.md) - check if the value is an unsigned integer number
+- [is_number_unsigned()](is_number_unsigned.md) check if the value is an unsigned integer number
-- [`is_number_float()`](is_number_float.md) - check if the value is a floating-point number
+- [is_number_float()](is_number_float.md) check if the value is a floating-point number
-- [`basic_json_view::is_number_integer`](../basic_json_view/is_number_integer.md) - the same check on a zero-copy view
+- [basic_json_view::is_number_integer](../basic_json_view/is_number_integer.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
-- [Number Handling](../../features/types/number_handling.md) - how numbers are stored and converted
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_number_unsigned.md

@@ -40,12 +40,10 @@ Constant.
 
 ## See also
 
-- [`is_number()`](is_number.md) - check if the value is a number
+- [is_number()](is_number.md) check if the value is a number
-- [`is_number_integer()`](is_number_integer.md) - check if the value is an integer or unsigned integer number
+- [is_number_integer()](is_number_integer.md) check if the value is an integer or unsigned integer number
-- [`is_number_float()`](is_number_float.md) - check if the value is a floating-point number
+- [is_number_float()](is_number_float.md) check if the value is a floating-point number
-- [`basic_json_view::is_number_unsigned`](../basic_json_view/is_number_unsigned.md) - the same check on a zero-copy view
+- [basic_json_view::is_number_unsigned](../basic_json_view/is_number_unsigned.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
-- [Number Handling](../../features/types/number_handling.md) - how numbers are stored and converted
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_object.md

@@ -36,12 +36,11 @@ Constant.
 
 ## See also
 
-- [`is_array`](is_array.md) - checks whether the JSON value is an array
+- [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)
+- [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
+- [type](type.md) returns the type of the JSON value
-- [`object_t`](object_t.md) - the type used to store JSON objects
+- [object_t](object_t.md) the type used to store JSON objects
-- [`basic_json_view::is_object`](../basic_json_view/is_object.md) - the same check on a zero-copy view
+- [basic_json_view::is_object](../basic_json_view/is_object.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_primitive.md

@@ -56,14 +56,13 @@ This library extends primitive types to binary types, because binary types are r
 
 ## See also
 
-- [`is_structured()`](is_structured.md) - returns whether the JSON value is structured
+- [is_structured()](is_structured.md) returns whether the JSON value is structured
-- [`is_null()`](is_null.md) - returns whether the JSON value is `null`
+- [is_null()](is_null.md) returns whether the JSON value is `null`
-- [`is_string()`](is_string.md) - returns whether the JSON value is a string
+- [is_string()](is_string.md) returns whether the JSON value is a string
-- [`is_boolean()`](is_boolean.md) - returns whether the JSON value is a boolean
+- [is_boolean()](is_boolean.md) returns whether the JSON value is a boolean
-- [`is_number()`](is_number.md) - returns whether the JSON value is a number
+- [is_number()](is_number.md) returns whether the JSON value is a number
-- [`is_binary()`](is_binary.md) - returns whether the JSON value is a binary array
+- [is_binary()](is_binary.md) returns whether the JSON value is a binary array
-- [`basic_json_view::is_primitive`](../basic_json_view/is_primitive.md) - the same check on a zero-copy view
+- [basic_json_view::is_primitive](../basic_json_view/is_primitive.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_string.md

@@ -36,11 +36,10 @@ Constant.
 
 ## See also
 
-- [`is_primitive`](is_primitive.md) - checks whether the JSON value is primitive
+- [is_primitive](is_primitive.md) checks whether the JSON value is primitive
-- [`type`](type.md) - returns the type of the JSON value
+- [type](type.md) returns the type of the JSON value
-- [`string_t`](string_t.md) - the type used to store JSON strings
+- [string_t](string_t.md) the type used to store JSON strings
-- [`basic_json_view::is_string`](../basic_json_view/is_string.md) - the same check on a zero-copy view
+- [basic_json_view::is_string](../basic_json_view/is_string.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/is_structured.md

@@ -54,11 +54,10 @@ Note that though strings are containers in C++, they are treated as primitive va
 
 ## See also
 
-- [`is_primitive()`](is_primitive.md) - returns whether JSON value is primitive
+- [is_primitive()](is_primitive.md) returns whether JSON value is primitive
-- [`is_array()`](is_array.md) - returns whether the value is an array
+- [is_array()](is_array.md) returns whether the value is an array
-- [`is_object()`](is_object.md) - returns whether the value is an object
+- [is_object()](is_object.md) returns whether the value is an object
-- [`basic_json_view::is_structured`](../basic_json_view/is_structured.md) - the same check on a zero-copy view
+- [basic_json_view::is_structured](../basic_json_view/is_structured.md) - the same check on a zero-copy view
-- [Types](../../features/types/index.md) - the JSON value types and how they are stored
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/items.md

@@ -54,7 +54,7 @@ using element_type = decltype(*j_object.items().begin());
 ```
 
 The per-element type (`iteration_proxy_value`) lives in the library's internal `detail` namespace and is
-intentionally unspecified as a stable, named type — `decltype` is the supported way to obtain it, but its exact
+intentionally unspecified as a stable, named type -- `decltype` is the supported way to obtain it, but its exact
 name/definition may change between versions.
 
 ## Return value
@@ -97,11 +97,10 @@ When iterating over an array, `key()` will return the index of the element as st
 
 ## See also
 
-- [`begin`](begin.md) - returns an iterator to the first element
+- [begin](begin.md) returns an iterator to the first element
-- [`end`](end.md) - returns an iterator to one past the last element
+- [end](end.md) returns an iterator to one past the last element
-- [`basic_json_view::items`](../basic_json_view/items.md) - the same range on a zero-copy view (`#!cpp const auto`,
+- [basic_json_view::items](../basic_json_view/items.md) - the same range on a zero-copy view (`#!cpp const auto`,
   not `#!cpp const auto&`: items are produced on the fly; document order, not sorted; duplicate keys are visited)
-- [Iterators](../../features/iterators.md#access-object-keys-during-iteration) - the article on iterating over keys and values
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/json_base_class_t.md

@@ -57,7 +57,7 @@ same name. Hidden members remain accessible via [`as_base_class`](as_base_class.
 
 ## See also
 
-- [`as_base_class`](as_base_class.md) - access the custom base class
+- [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

docs/mkdocs/docs/api/basic_json/json_serializer.md

@@ -44,11 +44,10 @@ deserializes. See [Template Parameter Requirements](../../features/types/templat
 
 ## See also
 
-- [`adl_serializer`](../adl_serializer/index.md) - the default `json_serializer`
+- [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](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
+- [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
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `JSONSerializer` template parameter
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/max_size.md

@@ -33,7 +33,7 @@ constant complexity.
 
 ## Notes
 
-This function does not return the maximal length of a string stored as JSON value — it returns the maximal number of
+This function does not return the maximal length of a string stored as JSON value -- it returns the maximal number of
 string elements the JSON value can store which is `1`.
 
 ## Examples
@@ -56,9 +56,9 @@ string elements the JSON value can store which is `1`.
 
 ## See also
 
-- [`size`](size.md) - returns the number of elements
+- [size](size.md) returns the number of elements
-- [`array_t`](array_t.md) - the type used to store JSON arrays
+- [array_t](array_t.md) the type used to store JSON arrays
-- [`object_t`](object_t.md) - the type used to store JSON objects
+- [object_t](object_t.md) the type used to store JSON objects
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/merge_diff.md

@@ -70,10 +70,9 @@ object operation (looking up a key, or adding one to the patch): logarithmic for
 
 ## See also
 
-- [RFC 7396 (JSON Merge Patch)](https://tools.ietf.org/html/rfc7396) - specification of JSON Merge Patch
+- [RFC 7396 (JSON Merge Patch)](https://tools.ietf.org/html/rfc7396)
-- [`merge_patch`](merge_patch.md) - applies a JSON Merge Patch
+- [merge_patch](merge_patch.md) applies a JSON Merge Patch
-- [`diff`](diff.md) - creates a diff as a JSON Patch
+- [diff](diff.md) creates a diff as a JSON Patch
-- [JSON Merge Patch](../../features/merge_patch.md) - the article on JSON Merge Patch
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/merge_patch.md

@@ -39,33 +39,13 @@ Basic guarantee: if an exception is thrown during the operation, the JSON value
 
 ## Complexity
 
-Linear in the total number of values (including nested ones) in `apply_patch`, times the cost of a key-based object
+Linear in the lengths of `apply_patch`.
-operation (looking up, adding, or erasing a member): logarithmic for [`json`](../json.md), and linear for
-[`ordered_json`](../ordered_json.md) (see [`ordered_map` complexity](../ordered_map.md#complexity)). For
-`ordered_json`, patching an object that has `n` members with a patch that has `m` members therefore takes O(n·m). The
-cost also includes one copy of `apply_patch` (see the notes below).
 
 ## Notes
 
-- `apply_patch` may be `#!cpp *this` itself or refer to a value contained in `#!cpp *this` (for example, a subobject
+`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
+returned by `#!cpp (*this)[key]`); it is read as it was when `merge_patch()` was called, before any modification of
-  `#!cpp *this`. To make this possible, the function copies `apply_patch` before it modifies `#!cpp *this`, so the cost
+`#!cpp *this`.
-  includes one copy of the patch.
-- A merge patch uses `#!json null` to remove a member, so it cannot set a member to `#!json null`: applying
-  `#!json {"a":null}` to `#!json {"a":1}` gives `#!json {}`.
-- Arrays are not merged: an array in the patch replaces the target value as a whole, and a `#!json null` inside an
-  array is kept as an element. `#!json null` members of the target that the patch does not mention are preserved.
-- A `#!json null` in the patch only removes a member; it does not prevent the creation of the enclosing objects.
-  Applying `#!json {"a":{"b":null}}` to `#!json {}` gives `#!json {"a":{}}` (see example 15 in Appendix A of the RFC).
-- If `apply_patch` is not an object, it replaces the target as a whole. In particular, a `#!json null` patch turns the
-  target into `#!json null`. If `apply_patch` is an object and the target is not, the target is first replaced by an
-  empty object, so applying `#!json {}` to `#!json 1` gives `#!json {}`.
-- A merge patch cannot express every change; for example, it cannot reorder array elements or remove a specific array
-  element. Use [JSON Patch](../../features/json_patch.md) ([RFC 6902](https://tools.ietf.org/html/rfc6902)) for that.
-  [`merge_diff`](merge_diff.md) has a matching limitation, see its notes.
-- A [discarded](is_discarded.md) value is treated like any other non-object value: a discarded
-  `apply_patch` turns the target into a discarded value, and an object patch replaces a discarded target by an object
-  as described above.
 
 ## Examples
 
@@ -85,10 +65,9 @@ cost also includes one copy of `apply_patch` (see the notes below).
 
 ## See also
 
-- [RFC 7396 (JSON Merge Patch)](https://tools.ietf.org/html/rfc7396) - specification of JSON Merge Patch
+- [RFC 7396 (JSON Merge Patch)](https://tools.ietf.org/html/rfc7396)
-- [`patch`](patch.md) - apply a JSON patch
+- [patch](patch.md) apply a JSON patch
-- [`merge_diff`](merge_diff.md) - creates a diff as a JSON Merge Patch
+- [merge_diff](merge_diff.md) creates a diff as a JSON Merge Patch
-- [JSON Merge Patch](../../features/merge_patch.md) - the article on JSON Merge Patch
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/meta.md

@@ -48,11 +48,8 @@ Constant.
 
 ## See also
 
-- [`NLOHMANN_JSON_VERSION_MAJOR`](../macros/nlohmann_json_version_major.md) /
+- [**NLOHMANN_JSON_VERSION_MAJOR**/**NLOHMANN_JSON_VERSION_MINOR**/**NLOHMANN_JSON_VERSION_PATCH**](../macros/nlohmann_json_version_major.md)
-  [`NLOHMANN_JSON_VERSION_MINOR`](../macros/nlohmann_json_version_major.md) /
+  \- library version information
-  [`NLOHMANN_JSON_VERSION_PATCH`](../macros/nlohmann_json_version_major.md) - library version information
-- [Integration](../../integration/index.md) - integrate the library
-- [Supported Macros](../../features/macros.md) - guide to all supported macros
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/number_float_t.md

@@ -84,11 +84,10 @@ Floating-point number values are stored directly inside a `basic_json` type.
 
 ## See also
 
-- [`number_integer_t`](number_integer_t.md) - the type used to store JSON integer numbers
+- [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
+- [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
+- [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
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the number template parameters
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/number_integer_t.md

@@ -80,11 +80,10 @@ Integer number values are stored directly inside a `basic_json` type.
 
 ## See also
 
-- [`number_unsigned_t`](number_unsigned_t.md) - the type used to store JSON unsigned integer numbers
+- [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
+- [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
+- [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
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the number template parameters
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/number_unsigned_t.md

@@ -82,11 +82,10 @@ Integer number values are stored directly inside a `basic_json` type.
 
 ## See also
 
-- [`number_integer_t`](number_integer_t.md) - the type used to store JSON integer numbers
+- [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
+- [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
+- [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
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the number template parameters
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/object_comparator_t.md

@@ -27,10 +27,8 @@ and [`default_object_comparator_t`](default_object_comparator_t.md) otherwise.
 
 ## See also
 
-- [`object_t`](object_t.md) - the type used to store JSON objects
+- [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
+- [default_object_comparator_t](default_object_comparator_t.md) the fallback comparator used when `object_t` has no `key_compare` member type
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `ObjectType` template parameter
-- [Object order](../../features/object_order.md) - preserve the insertion order of keys
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/object_t.md

@@ -20,7 +20,7 @@ To store objects in C++, a type is defined by the template parameters described
 `ObjectType`
 :   the container to store objects. Its template parameters must have the same order and meaning as those of
     `std::map`; in particular, the third parameter is a comparator. `#!cpp std::unordered_map`, whose third parameter
-    is a hash function, therefore needs an adapter — see
+    is a hash function, therefore needs an adapter -- see
     [Template Parameter Requirements](../../features/types/template_parameters.md#objecttype) for the full list of
     requirements, an adapter example, and the containers that are known to work.
 
@@ -125,12 +125,10 @@ the object is silently converted as an array of key-value pairs, which is incorr
 
 ## See also
 
-- [`array_t`](array_t.md) - the type used to store JSON arrays
+- [array_t](array_t.md) the type used to store JSON arrays
-- [`string_t`](string_t.md) - the type used to store JSON strings
+- [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_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
-- [Types](../../features/types/index.md) - how objects are stored
-- [Template Parameter Requirements](../../features/types/template_parameters.md) - requirements on the `ObjectType` template parameter
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator+=.md

@@ -123,9 +123,8 @@ interpreted as `object_t::value_type` or `std::initializer_list<basic_json>`, se
 
 ## See also
 
-- [`emplace_back`](emplace_back.md) - add a value to an array
+- [emplace_back](emplace_back.md) add a value to an array
-- [`push_back`](push_back.md) - add a value to an array/object
+- [push_back](push_back.md) add a value to an array/object
-- [Modifying values](../../features/modifying_values.md) - the article on modifying values
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator=.md

@@ -45,9 +45,8 @@ Linear.
 
 ## See also
 
-- [`basic_json`](basic_json.md) - create a JSON value
+- [basic_json](basic_json.md) create a JSON value
-- [`swap`](swap.md) - exchanges the contents of two JSON values
+- [swap](swap.md) exchanges the contents of two JSON values
-- [Creating JSON values](../../features/creating_values.md) - ways to create and assign JSON values
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator[].md

@@ -92,20 +92,12 @@ Strong exception safety: if an exception occurs, the original value stays intact
     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.
 
-    If the **non-const** version throws, the value is left unchanged: values it created for earlier reference tokens
-    of `ptr` are removed again. This also holds for exceptions such as `#!cpp std::bad_alloc` or
-    `#!cpp std::length_error` thrown while padding an array up to a very large index. With custom
-    [template parameters](../../features/types/template_parameters.md), this requires that `erase()` of the object and
-    array types and the move operations of the custom base class do not throw.
-
 ## Complexity
 
 1. Constant if `idx` is in the range of the array. Otherwise, linear in `idx - size()`.
 2. Logarithmic in the size of the container.
 3. Logarithmic in the size of the container.
-4. Linear in the number of reference tokens of `ptr`; for each of them, logarithmic in the size of the object, or
+4. Logarithmic in the size of the container.
-   constant for an array. When the non-const version pads an array with `#!json null` values, it is additionally
-   linear in `idx - size()` for that array.
 
 ## Notes
 
@@ -145,21 +137,10 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
         When the JSON pointer traverses intermediate levels that don't exist at all yet (not just a missing
         leaf), each missing level is created as an array or an object depending on whether the corresponding
-        pointer token is a valid array index: the token `0`, a sequence of digits that does not begin with `0`,
+        pointer token parses as a non-negative integer: a numeric token creates an array, a non-numeric token
-        or the token `-` creates an array, and every other token creates an object. For example, on an
+        creates an object. For example, on an initially `#!json null` value, `/foo/0/0/0` creates nested arrays,
-        initially `#!json null` value, `/foo/0/0/0` creates nested arrays, while `/foo/one/one/one` creates
+        while `/foo/one/one/one` creates nested objects. This is not specified by the JSON Pointer RFC; it is
-        nested objects. Tokens such as `01` or the empty token cannot be array indices (cf. RFC 6901, Sect. 4)
+        this library's own, intentional disambiguation rule. See also [JSON Pointer](../../features/json_pointer.md).
-        and therefore create objects, just as they would if the level already existed as an object. 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 "Large array indices"
-
-        As the array is filled up with `#!json null` values to the given index, the memory used grows with the index
-        and not with the size of the pointer: on a 64-bit platform, the index `10000000` allocates about 160 MB.
-        The library does not limit the index, so check the array indices of a JSON pointer from untrusted input
-        before using it with the non-const version. See
-        [Parsing untrusted input](../../features/parsing/untrusted_input.md#json-pointers-and-flattened-keys).
 
 !!! warning "Deprecation"
 
@@ -290,15 +271,13 @@ Strong exception safety: if an exception occurs, the original value stays intact
 
 ## See also
 
-- [Unchecked access](../../features/element_access/unchecked_access.md) - element access without range checking
+- documentation on [unchecked access](../../features/element_access/unchecked_access.md)
-- [Runtime assertions](../../features/assertions.md) - assertions guarding against undefined behavior
+- documentation on [runtime assertions](../../features/assertions.md)
-- [`at`](at.md) - access by reference with range checking
+- see [`at`](at.md) for access by reference with range checking
-- [`value`](value.md) - access with default value
+- see [`value`](value.md) for access with default value
-- [`basic_json_view::operator[]`](../basic_json_view/operator%5B%5D.md) - the same access on a zero-copy view (a duplicate
+- [basic_json_view::operator[]](../basic_json_view/operator%5B%5D.md) - the same access on a zero-copy view (a duplicate
   key resolves to the first member, whereas `parse()` keeps the last; a missing key gives a discarded view instead of
   undefined behavior)
-- [Element Access](../../features/element_access/index.md) - overview of all ways to access elements
-- [JSON Pointer](../../features/json_pointer.md) - access nested values with a pointer
 
 ## Version history
 
@@ -312,6 +291,4 @@ Strong exception safety: if an exception occurs, the original value stays intact
 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. Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) instead of
 [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) for a one-character array index that is not
-a digit (e.g., `/x`) in version 3.13.0, as it already did for longer ones. Fixed in version 3.13.0 to leave the value
+a digit (e.g., `/x`) in version 3.13.0, as it already did for longer ones.
-unchanged if the non-const version throws (strong exception safety, as documented); before, values created for earlier
-reference tokens of `ptr` were kept.

docs/mkdocs/docs/api/basic_json/operator_ValueType.md

@@ -84,7 +84,7 @@ Linear in the size of the JSON value.
 
 ## See also
 
-- [`get`](get.md) - get a value (explicit conversion)
+- [get](get.md) get a value (explicit conversion)
 - [Converting values](../../features/conversions.md) - the type conversions article
 
 ## Version history

docs/mkdocs/docs/api/basic_json/operator_eq.md

@@ -168,9 +168,9 @@ Linear.
 
 ## See also
 
-- [`operator!=`](operator_ne.md) - compare for inequality
+- [operator!=](operator_ne.md) compare for inequality
-- [`operator<=>`](operator_spaceship.md) - comparison: 3-way (C++20)
+- [operator<=>](operator_spaceship.md) comparison: 3-way (C++20)
-- [`basic_json_view::operator==`](../basic_json_view/operator_eq.md) - the same comparison on a zero-copy view, without
+- [basic_json_view::operator==](../basic_json_view/operator_eq.md) - the same comparison on a zero-copy view, without
   building a `basic_json` value for it
 
 ## Version history

docs/mkdocs/docs/api/basic_json/operator_ge.md

@@ -93,7 +93,7 @@ Linear.
 
 ## See also
 
-- [`operator<=>`](operator_spaceship.md) - comparison: 3-way
+- [**operator<=>**](operator_spaceship.md) comparison: 3-way
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator_gt.md

@@ -83,7 +83,7 @@ Linear.
 
 ## See also
 
-- [`operator<=>`](operator_spaceship.md) - comparison: 3-way
+- [**operator<=>**](operator_spaceship.md) comparison: 3-way
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator_le.md

@@ -94,7 +94,7 @@ Linear.
 
 ## See also
 
-- [`operator<=>`](operator_spaceship.md) - comparison: 3-way
+- [**operator<=>**](operator_spaceship.md) comparison: 3-way
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator_lt.md

@@ -94,7 +94,7 @@ Linear.
 
 ## See also
 
-- [`operator<=>`](operator_spaceship.md) - comparison: 3-way
+- [**operator<=>**](operator_spaceship.md) comparison: 3-way
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator_ne.md

@@ -93,9 +93,9 @@ Linear.
 
 ## See also
 
-- [`operator==`](operator_eq.md) - comparison: equal
+- [operator==](operator_eq.md) comparison: equal
-- [`operator<=>`](operator_spaceship.md) - comparison: 3-way (C++20)
+- [operator<=>](operator_spaceship.md) comparison: 3-way (C++20)
-- [`basic_json_view::operator!=`](../basic_json_view/operator_ne.md) - the same comparison on a zero-copy view, without
+- [basic_json_view::operator!=](../basic_json_view/operator_ne.md) - the same comparison on a zero-copy view, without
   building a `basic_json` value for it
 
 ## Version history

docs/mkdocs/docs/api/basic_json/operator_spaceship.md

@@ -88,12 +88,12 @@ Linear.
 
 ## See also
 
-- [`operator==`](operator_eq.md) - comparison: equal
+- [**operator==**](operator_eq.md) - comparison: equal
-- [`operator!=`](operator_ne.md) - comparison: not equal
+- [**operator!=**](operator_ne.md) - comparison: not equal
-- [`operator<`](operator_lt.md) - comparison: less than
+- [**operator<**](operator_lt.md) - comparison: less than
-- [`operator<=`](operator_le.md) - comparison: less than or equal
+- [**operator<=**](operator_le.md) - comparison: less than or equal
-- [`operator>`](operator_gt.md) - comparison: greater than
+- [**operator>**](operator_gt.md) - comparison: greater than
-- [`operator>=`](operator_ge.md) - comparison: greater than or equal
+- [**operator>=**](operator_ge.md) - comparison: greater than or equal
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/operator_value_t.md

@@ -49,9 +49,8 @@ Constant.
 
 ## See also
 
-- [`type`](type.md) - named member function equivalent to this implicit conversion operator
+- [type](type.md) named member function equivalent to this implicit conversion operator
-- [`value_t`](value_t.md) - the enumeration of JSON types
+- [value_t](value_t.md) the enumeration of JSON types
-- [Types](../../features/types/index.md) - the JSON value types
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/other_error.md

@@ -40,9 +40,6 @@ classDiagram
     style json_other_error fill:#CCCCFF
 ```
 
-<p class="nj-caption" markdown>Class hierarchy of the library's exceptions; arrows point from a derived class to its
-base class, and the highlighted box is `basic_json::other_error`.</p>
-
 ## Member functions
 
 - **what** - returns explanatory string
@@ -69,14 +66,12 @@ base class, and the highlighted box is `basic_json::other_error`.</p>
 
 ## See also
 
-- [`exception`](exception.md) - the base class of all exceptions thrown by the library
+- [`exception`](exception.md) for the base class of all exceptions thrown by the library
-- [List of other errors](../../home/exceptions.md#further-exceptions) - overview of further errors (`other_error`)
+- [List of other errors](../../home/exceptions.md#further-exceptions)
-- [`parse_error`](parse_error.md) - exceptions indicating a parse error
+- [`parse_error`](parse_error.md) for exceptions indicating a parse error
-- [`invalid_iterator`](invalid_iterator.md) - exceptions indicating errors with iterators
+- [`invalid_iterator`](invalid_iterator.md) for exceptions indicating errors with iterators
-- [`type_error`](type_error.md) - exceptions indicating executing a member function with a wrong type
+- [`type_error`](type_error.md) for exceptions indicating executing a member function with a wrong type
-- [`out_of_range`](out_of_range.md) - exceptions indicating access out of the defined range
+- [`out_of_range`](out_of_range.md) for exceptions indicating access out of the defined range
-- [Exceptions](../../home/exceptions.md) - all exceptions and their error codes
-- [`JSON_DIAGNOSTICS`](../macros/json_diagnostics.md) - extended exception messages with the path of the failing value
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json/out_of_range.md

@@ -41,9 +41,6 @@ classDiagram
     style json_out_of_range fill:#CCCCFF
 ```
 
-<p class="nj-caption" markdown>Class hierarchy of the library's exceptions; arrows point from a derived class to its
-base class, and the highlighted box is `basic_json::out_of_range`.</p>
-
 ## Member functions
 
 - **what** - returns explanatory string
@@ -70,15 +67,12 @@ base class, and the highlighted box is `basic_json::out_of_range`.</p>
 
 ## See also
 
-- [`exception`](exception.md) - the base class of all exceptions thrown by the library
+- [`exception`](exception.md) for the base class of all exceptions thrown by the library
-- [List of out-of-range errors](../../home/exceptions.md#out-of-range) - overview of out-of-range errors
+- [List of out-of-range errors](../../home/exceptions.md#out-of-range)
-  (`out_of_range`)
+- [`parse_error`](parse_error.md) for exceptions indicating a parse error
-- [`parse_error`](parse_error.md) - exceptions indicating a parse error
+- [`invalid_iterator`](invalid_iterator.md) for exceptions indicating errors with iterators
-- [`invalid_iterator`](invalid_iterator.md) - exceptions indicating errors with iterators
+- [`type_error`](type_error.md) for exceptions indicating executing a member function with a wrong type
-- [`type_error`](type_error.md) - exceptions indicating executing a member function with a wrong type
+- [`other_error`](other_error.md) for exceptions indicating other library errors
-- [`other_error`](other_error.md) - exceptions indicating other library errors
-- [Exceptions](../../home/exceptions.md) - all exceptions and their error codes
-- [`JSON_DIAGNOSTICS`](../macros/json_diagnostics.md) - extended exception messages with the path of the failing value
 
 ## Version history