Regenerate the amalgamated headers

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

.github/labeler.yml

@@ -63,12 +63,12 @@ labels:
     - "single_include/nlohmann/json_view\\.hpp"
     - "tests/src/unit-json_view.*"
     - "tests/src/json_view_test_helpers\\.hpp"
-    - "tests/src/fuzzer-(parse_json_view|json_view_image)\\.cpp"
+    - "tests/src/fuzzer-parse_json_view\\.cpp"
     - "tools/amalgamate/config_json_view\\.json"
     - "docs/mkdocs/docs/features/json_view\\.md"
     - "docs/mkdocs/docs/api/basic_json_(document|view)/.*"
-    - "docs/mkdocs/docs/api/(ordered_)?json_(editable_)?(document|view)\\.md"
-    - "docs/mkdocs/docs/examples/(basic_json_(document|view)__|(ordered_)?json_(editable_)?(document|view)).*"
+    - "docs/mkdocs/docs/api/(ordered_)?json_(document|view)\\.md"
+    - "docs/mkdocs/docs/examples/(basic_json_(document|view)__|(ordered_)?json_(document|view)).*"
     - "tests/benchmarks/src/benchmarks_view\\.cpp"
 
 - label: "aspect: json_view"

.github/workflows/check_amalgamation.yml

@@ -77,12 +77,13 @@ jobs:
           cd $MAIN_DIR
 
           # Built from this PR's own tools/macro_builder/main.cpp, not a
-          # develop checkout: unlike amalgamate.py, this tool has no other
-          # source of truth to check against (its own README documents that
-          # it must reproduce macro_scope.hpp byte for byte), so there is
-          # nothing to gain from checking out a separate copy, and doing so
-          # would make this step fail on a PR that adds support for a new
-          # dispatch table until that PR itself merges to develop.
+          # develop checkout: unlike amalgamate.py and generate_natvis.py,
+          # this tool has no other source of truth to check against (its
+          # own README documents that it must reproduce macro_scope.hpp
+          # byte for byte), so there is nothing to gain from checking out a
+          # separate copy, and doing so would make this step fail on a PR
+          # that adds support for a new dispatch table until that PR itself
+          # merges to develop.
           TMPDIR=$(mktemp -d ./macro_builder_check.XXXXXX)
           c++ -std=c++11 tools/macro_builder/main.cpp -o "$TMPDIR/macro_builder"
           "$TMPDIR/macro_builder" > "$TMPDIR/paste.hpp"
@@ -145,14 +146,14 @@ jobs:
       - name: Regenerate nlohmann_json.natvis
         run: |
           cd $MAIN_DIR
-          # The generator and its template are what this check verifies the
-          # committed natvis file against (which namespaces it lists, and
-          # what each entry looks like), so run this PR's copy rather than
-          # the develop checkout's: with develop's, a PR that changes either
-          # could never pass. generate_natvis.py loads the template from its
-          # own directory. Like the macro_builder step above, this only runs
-          # PR content in a job without credentials.
-          python3 tools/generate_natvis/generate_natvis.py $MAIN_DIR
+          # The template is what this check verifies the committed natvis
+          # file against, so take it from this PR rather than from the
+          # develop checkout: generate_natvis.py loads the template from its
+          # own directory, and with develop's copy a PR that changes the
+          # template could never pass. Like the macro_builder step above,
+          # this only renders PR content in a job without credentials.
+          cp tools/generate_natvis/nlohmann_json.natvis.j2 $NATVIS_TOOL_DIR/
+          python3 $NATVIS_TOOL_DIR/generate_natvis.py $MAIN_DIR
 
       - name: Build patch and check for differences
         id: diff

.github/workflows/check_api_docs.yml

@@ -1,81 +0,0 @@
-name: "Check API documentation"
-
-on:
-  pull_request:
-
-permissions:
-  contents: read
-
-jobs:
-  check_api_docs:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Harden Runner
-        uses: step-security/harden-runner@bf7454d06d71f1098171f2acdf0cd4708d7b5920 # v2.20.0
-        with:
-          egress-policy: audit
-
-      - name: Checkout pull request
-        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
-
-      - name: Install clang
-        # Used only as a subprocess for `clang++ -E -v` system-include-path discovery in
-        # extract_api.py; it does not need to version-match the pinned libclang pip wheel
-        # below, which does the actual AST parsing. Do not "fix" this to be version-matched.
-        run: sudo apt-get update && sudo apt-get install -y clang
-
-      - name: Install Python dependencies
-        run: pip install -r tools/api_checker/requirements.txt
-
-      - name: Extract API and regenerate the committed surface file
-        run: |
-          python3 tools/api_checker/extract_api.py \
-            --header include/nlohmann/json.hpp \
-            --include include \
-            --output /tmp/api_snapshot.json \
-            --surface-output tools/api_checker/api_surface.json
-
-      - name: "Check API documentation (Phase 1: advisory)"
-        # Surfaces missing/broken @sa links without failing the job while the backlog from the
-        # initial AST-based rollout is burned down. See tools/api_checker/POLICY.md and the PR
-        # that introduced this workflow for the two-phase rollout plan.
-        continue-on-error: true
-        run: |
-          python3 tools/api_checker/check_docs.py \
-            --snapshot /tmp/api_snapshot.json
-
-      - name: Check macro documentation (advisory only)
-        # Cross-checks docs/mkdocs/docs/api/macros/ pages against #define sites. Only checks the
-        # documented-macro-still-exists direction; never blocks CI. See POLICY.md.
-        run: python3 tools/api_checker/check_macros.py
-
-      - name: Check for uncommitted API surface changes
-        id: diff
-        run: |
-          mkdir -p ${{ github.workspace }}/patch
-          git diff --patch --no-color -- tools/api_checker/api_surface.json > ${{ github.workspace }}/patch/api_surface.patch
-          if [ -s ${{ github.workspace }}/patch/api_surface.patch ]; then
-            echo "tools/api_checker/api_surface.json is out of date. Diff:"
-            cat ${{ github.workspace }}/patch/api_surface.patch
-            echo "has_diff=true" >> "$GITHUB_OUTPUT"
-          else
-            echo "has_diff=false" >> "$GITHUB_OUTPUT"
-          fi
-
-      # Uploaded so contributors can fix their PR with `git apply api_surface.patch`
-      # instead of installing libclang locally.
-      - name: Upload patch
-        if: steps.diff.outputs.has_diff == 'true'
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
-        with:
-          name: api-surface-patch
-          path: patch/api_surface.patch
-
-      - name: Fail if API surface file is not up to date
-        # Unlike the doc-backlog check above, this is purely mechanical regeneration with no
-        # backlog to phase in -- blocking from the start, matching check_amalgamation.yml's
-        # precedent. Contributors who add/remove/rename public API must regenerate and commit
-        # tools/api_checker/api_surface.json as part of their PR.
-        if: steps.diff.outputs.has_diff == 'true'
-        run: exit 1

.github/workflows/scorecards.yml

@@ -50,7 +50,7 @@ jobs:
           persist-credentials: false
 
       - name: "Run analysis"
-        uses: ossf/scorecard-action@fa7117db83c52d787ae5a89f350999701505d78e # v2.5.0
+        uses: ossf/scorecard-action@2d1146689b8cda280b9bc96326124645441f03bc # v2.4.4
         with:
           results_file: results.sarif
           results_format: sarif

.gitignore

@@ -3,7 +3,6 @@
 *.gcno
 *.gcda
 .DS_Store
-__pycache__/
 
 /.idea
 /cmake-build-*
@@ -45,10 +44,6 @@ venv
 
 nlohmann_json.spdx
 
-# api_checker: ephemeral, location/doc-status-sensitive working file (not the committed
-# release-tracking artifact -- see tools/api_checker/api_surface.json for that)
-/tools/api_checker/api_snapshot.json
-
 # Bazel-related
 MODULE.bazel.lock
 
@@ -65,6 +60,3 @@ MODULE.bazel.lock
 /json.tar.xz.asc
 /release_files/
 /single_include/nlohmann/*.asc
-
-# GCC module cache
-/gcm.cache/

BUILD.bazel

@@ -70,10 +70,7 @@ cc_library(
         "include/nlohmann/detail/view/builder.hpp",
         "include/nlohmann/detail/view/compare.hpp",
         "include/nlohmann/detail/view/document_data.hpp",
-        "include/nlohmann/detail/view/edit.hpp",
-        "include/nlohmann/detail/view/edit_storage.hpp",
         "include/nlohmann/detail/view/errors.hpp",
-        "include/nlohmann/detail/view/image.hpp",
         "include/nlohmann/detail/view/input.hpp",
         "include/nlohmann/detail/view/iterator.hpp",
         "include/nlohmann/detail/view/lookup.hpp",
@@ -82,11 +79,9 @@ cc_library(
         "include/nlohmann/detail/view/materialize.hpp",
         "include/nlohmann/detail/view/node.hpp",
         "include/nlohmann/detail/view/number.hpp",
-        "include/nlohmann/detail/view/object_index.hpp",
         "include/nlohmann/detail/view/pointer.hpp",
         "include/nlohmann/detail/view/scan.hpp",
         "include/nlohmann/detail/view/serializer.hpp",
-        "include/nlohmann/detail/view/simd.hpp",
         "include/nlohmann/detail/view/string_ref.hpp",
         "include/nlohmann/detail/view/value.hpp",
         "include/nlohmann/json.hpp",

README.md

@@ -105,7 +105,7 @@ Thanks everyone!
 
 :books: If you want to **learn more** about how to use the library, check out the rest of the [**README**](#examples), have a look at [**code examples**](https://github.com/nlohmann/json/tree/develop/docs/mkdocs/docs/examples), or browse through the [**help pages**](https://json.nlohmann.me).
 
-:construction: If you want to understand the **API** better, check out the [**API Reference**](https://json.nlohmann.me/api/basic_json/) or have a look at the [quick reference](#quick-reference) below. The public API surface is derived mechanically and checked for documentation coverage by the tooling in [`tools/api_checker/`](tools/api_checker/), whose [POLICY.md](tools/api_checker/POLICY.md) defines what counts as public API and what stability is guaranteed.
+:construction: If you want to understand the **API** better, check out the [**API Reference**](https://json.nlohmann.me/api/basic_json/) or have a look at the [quick reference](#quick-reference) below.
 
 :bug: If you found a **bug**, please check the [**FAQ**](https://json.nlohmann.me/home/faq/) if it is a known issue or the result of a design decision. Please also have a look at the [**issue list**](https://github.com/nlohmann/json/issues) before you [**create a new issue**](https://github.com/nlohmann/json/issues/new/choose). Please provide as much information as possible to help us understand and reproduce your issue.
 
@@ -1410,7 +1410,6 @@ THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR I
 - The class contains parts of [Google Abseil](https://github.com/abseil/abseil-cpp) which is licensed under the [Apache 2.0 License](https://opensource.org/licenses/Apache-2.0).
 - The class contains an adapted version of the Eisel-Lemire algorithm, its table of powers of five, and its digit comparison for long numbers from [fast_float](https://github.com/fastfloat/fast_float) by Daniel Lemire and contributors, which is available under the [MIT License](https://opensource.org/licenses/MIT) (used here), the Apache 2.0 License, and the Boost Software License. Copyright © 2021 The fast_float authors
 - The view's parser (`<nlohmann/json_view.hpp>`) contains techniques and code adapted from [yyjson](https://github.com/ibireme/yyjson) by YaoYuan, which is licensed under the [MIT License](https://opensource.org/licenses/MIT) (see above): table-driven decoding of `\u` escapes and fixed-offset unrolled checks.
-- The view's parser (`<nlohmann/json_view.hpp>`) validates non-ASCII strings with the vector UTF-8 check of [simdjson](https://github.com/simdjson/simdjson) by Daniel Lemire, Geoff Langdale, John Keiser, and contributors (its "lookup4" algorithm and tables, after J. Keiser and D. Lemire, "Validating UTF-8 In Less Than One Instruction Per Byte", 2021), which is available under the [MIT License](https://opensource.org/licenses/MIT) (used here) and the Apache 2.0 License. Copyright &copy; 2018-2025 The simdjson authors
 
 <img align="right" src="https://git.fsfe.org/reuse/reuse-ci/raw/branch/master/reuse-horizontal.png" alt="REUSE Software">
 

cmake/requirements/requirements-cppcheck.txt

@@ -1 +1 @@
-cppcheck==1.5.3
+cppcheck==1.5.2

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

@@ -485,10 +485,8 @@ basic_json(basic_json&& other) noexcept;
 1. Since version 1.0.0.
 2. Since version 1.0.0.
 3. Since version 2.1.0.
-4. Since version 3.2.0. Also initializes the position reported by
-   [`start_pos()`](start_pos.md)/[`end_pos()`](end_pos.md) from `val` when
-   [`JSON_DIAGNOSTIC_POSITIONS`](../macros/json_diagnostic_positions.md) is enabled, since version 3.12.0. Explicit
-   for different string types if `JSON_USE_IMPLICIT_CONVERSIONS` is `0` since version 3.13.0.
+4. Since version 3.2.0. Explicit for different string types if `JSON_USE_IMPLICIT_CONVERSIONS` is `0` since
+   version 3.13.0.
 5. Since version 1.0.0.
 6. Since version 1.0.0.
 7. Since version 1.0.0. Fixed in version 3.13.0 to also check the iterator range for binary values; before, a range

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

@@ -1,38 +0,0 @@
-# <small>nlohmann::basic_json::</small>bjdata_version_t
-
-```cpp
-enum class bjdata_version_t
-{
-    draft2,
-    draft3,
-};
-```
-
-This enumeration is used in the [`to_bjdata`](to_bjdata.md) function to choose which draft version of
-the BJData specification to encode ND-array extensions for:
-
-draft2
-:   encode using the BJData Draft 2 ND-array format
-
-draft3
-:   encode using the BJData Draft 3 ND-array format
-
-## Examples
-
-??? example
-
-    The example shows how `bjdata_version_t` selects the BJData draft used by `to_bjdata`.
-
-    ```cpp
-    --8<-- "examples/bjdata_version_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/bjdata_version_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.12.0.

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

@@ -1,32 +0,0 @@
-# <small>nlohmann::basic_json::</small>initializer_list_t
-
-```cpp
-using initializer_list_t = std::initializer_list<detail::json_ref<basic_json>>;
-```
-
-The type used for the initializer-list [constructor](basic_json.md) (overload 5) and for functions
-such as [`operator=`](operator=.md) that accept a braced-init-list of JSON values. Each element wraps a
-`basic_json` value or something convertible to one, deferring the decision of whether the list should be
-parsed as a JSON array or a JSON object to the constructor itself.
-
-See the [constructor](basic_json.md) documentation for how `initializer_list_t` values are interpreted.
-
-## Examples
-
-??? example
-
-    The example shows how an `initializer_list_t` is used to construct a JSON value.
-
-    ```cpp
-    --8<-- "examples/initializer_list_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/initializer_list_t.output"
-    ```
-
-## Version history
-
-- Since version 1.0.0.

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

@@ -1,31 +0,0 @@
-# <small>nlohmann::basic_json::</small>json_sax_t
-
-```cpp
-using json_sax_t = json_sax<basic_json>;
-```
-
-The [`json_sax`](../json_sax/index.md) interface bound to this `basic_json` specialization, i.e. with
-`BasicJsonType` fixed to `basic_json`. Used as the SAX interface type by [`sax_parse`](sax_parse.md) and
-other SAX-based parsing functions.
-
-See [`nlohmann::json_sax`](../json_sax/index.md) for more information.
-
-## Examples
-
-??? example
-
-    The example shows the type `json_sax_t`.
-
-    ```cpp
-    --8<-- "examples/json_sax_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/json_sax_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.2.0.

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

@@ -38,7 +38,7 @@ Strong guarantee: `source` and `target` are never modified.
 
 Linear in the total number of values (including nested ones) in `source` and `target`, times the cost of a key-based
 object operation (looking up a key, or adding one to the patch): logarithmic for [`json`](../json.md), and linear for
-[`ordered_json`](../ordered_json.md) (see [`ordered_map` complexity](../ordered_map/index.md#complexity)). 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)²).
 
 ## Notes

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

@@ -51,5 +51,3 @@ Linear.
 ## Version history
 
 - Added in version 1.0.0.
-- The `noexcept` specification was extended to also depend on
-  [`json_base_class_t`](json_base_class_t.md)'s move-assignment in version 3.11.3.

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

@@ -92,8 +92,3 @@ Linear in the size of the JSON value.
 - Since version 1.0.0.
 - Macros `JSON_EXPLICIT`/[`JSON_USE_IMPLICIT_CONVERSIONS`](../macros/json_use_implicit_conversions.md) added
   in version 3.9.0.
-- The exclusion of `std::any` from this conversion became conditional on
-  [`JSON_HAS_STATIC_RTTI`](../macros/json_has_static_rtti.md) in version 3.11.3.
-- `std::optional<T>` excluded from this conversion in version 3.13.0; use
-  [`get<std::optional<T>>()`](get.md)/[`get_to()`](get_to.md) instead (see
-  [Converting values](../../features/conversions.md)).

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

@@ -123,6 +123,4 @@ Linear in the size of the JSON value `j`.
   that is not valid UTF-8 unchanged, as before; `strict` (the default if
   [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316`.
 - Throws `type_error.321` for a discarded value since version 3.13.0; previously, a discarded value nested in an
-  array or object was silently skipped, producing invalid BJData.
-- Writes unsigned integers wider than 64 bits as high-precision numbers since version 3.13.0; previously, they were
-  silently truncated to 64 bits.
+  array or object was silently skipped, producing invalid BJData.

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

@@ -37,9 +37,8 @@ With (2), the bytes written before the exception remain in the output adapter.
 
 ## Exceptions
 
-- Throws [out_of_range.407](../../home/exceptions.md#jsonexceptionout_of_range407) if `j` contains an integer outside
-  the range of int64 (an unsigned integer above 9223372036854775807, or, with a number type wider than 64 bits, any
-  integer beyond int64), which BON8 cannot represent
+- Throws [out_of_range.407](../../home/exceptions.md#jsonexceptionout_of_range407) if `j` contains an unsigned integer
+  above 9223372036854775807, which BON8 cannot represent
 - Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if `j` contains a string that is not
   valid UTF-8
 - Throws [type_error.321](../../home/exceptions.md#jsonexceptiontype_error321) if `j` or a value nested in it is

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

@@ -47,10 +47,6 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 
 - Throws [`type_error.317`](../../home/exceptions.md#jsonexceptiontype_error317) if the top-level type of the JSON value
   is not an object; example: `"to serialize to BSON, top-level type must be object, but is string"`
-- Throws [`out_of_range.407`](../../home/exceptions.md#jsonexceptionout_of_range407) if `j` contains a signed integer
-  outside the range of int64 or an unsigned integer outside the range of uint64, which is only possible with a number
-  type wider than 64 bits; example:
-  `"integer number 9223372036854775808 cannot be represented by BSON as it does not fit int64"`
 - Throws [`out_of_range.409`](../../home/exceptions.md#jsonexceptionout_of_range409) if a key in the JSON object contains
   a null byte (code point U+0000); example: `"BSON key cannot contain code point U+0000 (at byte 2)"`
 - Throws [`out_of_range.412`](../../home/exceptions.md#jsonexceptionout_of_range412) if the length of a document, array,
@@ -123,5 +119,3 @@ pass before anything is written.
   that is not valid UTF-8 unchanged, as before; `strict` (the default if
   [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316` before anything
   is written.
-- Throws `out_of_range.407` for integers that do not fit 64 bits since version 3.13.0; previously, integers of a
-  number type wider than 64 bits were silently truncated.

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

@@ -46,9 +46,6 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 
 ## Exceptions
 
-- Throws [`out_of_range.407`](../../home/exceptions.md#jsonexceptionout_of_range407) if `j` contains an integer
-  outside [-2^64, 2^64-1], which is only possible with a number type wider than 64 bits; example:
-  `"integer number 18446744073709551616 cannot be represented by CBOR as it does not fit [-2^64, 2^64-1]"`
 - Throws [type_error.316](../../home/exceptions.md#jsonexceptiontype_error316) if a string or object key in `j` is
   not valid UTF-8 and `error_handler` is `strict` (the default only if
   [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled)
@@ -93,5 +90,3 @@ Linear in the size of the JSON value `j`.
   [`JSON_STRICT_BINARY_UTF8`](../macros/json_strict_binary_utf8.md) is enabled) throws `type_error.316`.
 - Throws `type_error.321` for a discarded value since version 3.13.0; previously, a discarded value nested in an
   array or object was silently skipped, producing invalid CBOR.
-- Throws `out_of_range.407` for integers that do not fit 64 bits since version 3.13.0; previously, integers of a
-  number type wider than 64 bits were silently truncated.

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

@@ -46,9 +46,6 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 
 ## Exceptions
 
-- Throws [`out_of_range.407`](../../home/exceptions.md#jsonexceptionout_of_range407) if `j` contains an integer
-  outside [-2^63, 2^64-1], which is only possible with a number type wider than 64 bits; example:
-  `"integer number 18446744073709551616 cannot be represented by MessagePack as it does not fit [-2^63, 2^64-1]"`
 - Throws [`out_of_range.412`](../../home/exceptions.md#jsonexceptionout_of_range412) if the length of a string, binary
   value, array, or object exceeds 4294967295, the maximum MessagePack can store; example:
   `"MessagePack length 4294967296 exceeds maximum of 4294967295"`
@@ -115,5 +112,3 @@ Linear in the size of the JSON value `j`.
   `number_unsigned_t`.
 - Throws `type_error.321` for a discarded value since version 3.13.0; previously, a discarded value nested in an
   array or object was silently skipped, producing invalid MessagePack.
-- Throws `out_of_range.407` for integers that do not fit 64 bits since version 3.13.0; previously, integers of a
-  number type wider than 64 bits were silently truncated.

docs/mkdocs/docs/api/basic_json_document/erase.md

@@ -1,129 +0,0 @@
-# <small>nlohmann::basic_json_document::</small>erase
-
-```cpp
-// (1)
-std::size_t erase(view_type object, string_view_t key);
-
-// (2)
-template<typename I>
-void erase(view_type array, I idx);
-
-// (3)
-std::size_t erase(const json_pointer& ptr);
-```
-
-Only an **editable** document (`#!cpp Editable == true`, e.g. [`json_editable_document`](../json_editable_document.md))
-has `erase`; calling it on a read-only `basic_json_document` fails to compile (`#!cpp static_assert`).
-
-1. Removes every member of `object` whose key is `key` (see [Notes](#notes) on duplicate keys) and returns how many
-   were removed; `#!cpp 0` if `object` has no member with this key.
-2. Removes the element at index `idx` of `array`, which must already exist (`#!cpp idx < array.size()`).
-3. Removes the value the JSON pointer `ptr` refers to, relative to [`root()`](root.md). `ptr` must not be empty
-   ([`root()`](root.md) itself cannot be erased), and the *parent* of the target must already exist. The target is
-   removed as in 1. if the parent is an object (returns the number of removed members, `#!cpp 0` or more) and as in 2.
-   if it is an array (always returns `#!cpp 1`).
-
-## Template parameters
-
-`I`
-:   an integral type other than `#!cpp bool`, deduced (overloads taking a `#!cpp bool` or a non-integral type for
-    `idx` do not participate in overload resolution).
-
-## Parameters
-
-`object` (in)
-:   the object to remove a member of
-
-`array` (in)
-:   the array to remove an element of
-
-`key` (in)
-:   the key of the member(s) to remove
-
-`idx` (in)
-:   the index of the element to remove; a negative value throws (see [Exceptions](#exceptions))
-
-`ptr` (in)
-:   a JSON pointer to the value to remove, relative to `root()`
-
-## Return value
-
-1. the number of removed members (`#!cpp 0` if `object` had none with this `key`)
-2. (nothing)
-3. the number of removed values (`#!cpp 0` or more for an object member, always `#!cpp 1` for an array element)
-
-## Exceptions
-
-1. Throws [`type_error.307`](../../home/exceptions.md#jsonexceptiontype_error307) if `object` is not an object -- the
-   same message [`BasicJsonType::erase`](../basic_json/erase.md) throws for the same type.
-2. Throws `type_error.307` if `array` is not an array. Throws
-   [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if `idx` is negative, or if
-   `#!cpp idx >= array.size()`.
-3. Throws [`out_of_range.405`](../../home/exceptions.md#jsonexceptionout_of_range405) ("JSON pointer has no parent")
-   if `ptr` is empty. Throws what [`at`](../basic_json_view/at.md) throws (overload 3) for resolving `ptr`'s parent.
-   For the last reference token itself: if the parent is an array, throws what 2. throws for an index that is out of
-   range, or, for a token that is not a valid array index,
-   [`parse_error.106`](../../home/exceptions.md#jsonexceptionparse_error106) (a leading `#!cpp '0'`),
-   [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) (not a number),
-   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) (too large for `size_type`), or
-   [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) (an empty token); otherwise (an
-   object, or a primitive value the pointer's parent resolves to) throws what 1. throws.
-
-Overloads 1. and 2. also throw [`invalid_iterator.202`](../../home/exceptions.md#jsonexceptioninvalid_iterator202)
-("view does not belong to this document") if `object`/`array` is a [discarded](../basic_json_view/is_discarded.md)
-view or a view of a *different* document. Overload 3. never throws `invalid_iterator.202`: it takes no view, and it
-always starts from this document's own [`root()`](root.md).
-
-## Complexity
-
-1. Linear in the number of members of `object`.
-2. Linear in the number of elements of `array` at or after `idx` (they move one slot over).
-3. Linear in the number of reference tokens of `ptr` and, for each token, in the number of members of the object at
-   that level or the index into the array (as [`at`](../basic_json_view/at.md)), plus the complexity of 1. or 2. for
-   the last token.
-
-## Notes
-
-!!! info "Duplicate keys"
-
-    Overload 1. removes *every* member with `key`, not just the first -- unlike [`set`](set.md), which assigns the
-    first occurrence and drops the rest. This is why it returns a count rather than a single view: there may be
-    more than one member removed, or none.
-
-Like [`set`](set.md) and [`push_back`](push_back.md), `erase` never moves an element's *value*: a view still
-referring to a removed member or element keeps showing what it last held (see [Edits](index.md#edits)) -- it just no
-longer appears when `array`/`object` is read, dumped, or iterated. What does change is the container's sequence of
-*links* to its elements: removing an element of `array` (2.) shifts the links to the elements after it by one, as
-[`insert`](insert.md) does in the other direction. *Every* iterator already taken over `array`/`object` is invalidated
-by an erase, not only those at or after the removed element, since the container may now use a different sequence.
-
-## Examples
-
-??? example
-
-    The example below drops a deprecated field and a decommissioned entry from a configuration document -- using all
-    three overloads -- and shows what stays intact that would not with a plain `json`/`ordered_json` value: the order
-    of the fields around the ones removed, and the exact spelling of a number that was never touched.
-
-    ```cpp
-    --8<-- "examples/basic_json_document__erase.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/basic_json_document__erase.output"
-    ```
-
-## See also
-
-- [insert](insert.md) - insert an element into an array
-- [set](set.md) - replace a value, or set an object member, an array element, or the value a JSON pointer refers to
-- [push_back](push_back.md) - append to an array
-- [root](root.md) - the view of the root value, the starting point of overload 3
-- [`BasicJsonType::erase`](../basic_json/erase.md) - the corresponding function of `basic_json`
-- [Edits](index.md#edits) - what an edit guarantees, for every overload
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_document/index.md

@@ -3,7 +3,7 @@
 <small>Defined in header `<nlohmann/json_view.hpp>`</small>
 
 ```cpp
-template<typename BasicJsonType, bool Editable = false>
+template<typename BasicJsonType>
 class basic_json_document;
 ```
 
@@ -20,11 +20,6 @@ is move-only: a copy would duplicate the whole index, the decoded-string buffer,
 enough in every use we know of. The index, the decoded strings, and the owned text live in one heap block that the
 document holds through a `#!cpp std::unique_ptr`; this is also why views survive a move of the document.
 
-With `#!cpp Editable == true`, the document also offers [`set`](set.md), [`push_back`](push_back.md),
-[`insert`](insert.md), and [`erase`](erase.md) to change values in place, see [Edits](#edits) below. The source text
-itself is never written; a read-only document (`#!cpp Editable == false`, the default) does not carry any of the
-bookkeeping edits need, and calling any of them on one fails to compile (`#!cpp static_assert`).
-
 ## Template parameters
 
 `BasicJsonType`
@@ -32,38 +27,23 @@ bookkeeping edits need, and calling any of them on one fails to compile (`#!cpp
     [`ordered_json`](../ordered_json.md). Only 64-bit `number_integer_t`/`number_unsigned_t` types are supported; this
     is checked with a `static_assert`.
 
-`Editable`
-:   whether the document supports [`set`](set.md), [`push_back`](push_back.md), [`insert`](insert.md), and
-    [`erase`](erase.md) (optional, `#!cpp false` by default). See [Edits](#edits) below.
-
 ## Specializations
 
-- [**json_document**](../json_document.md) - read-only documents of the default specialization [`json`](../json.md)
-- [**ordered_json_document**](../ordered_json_document.md) - read-only documents of
-  [`ordered_json`](../ordered_json.md)
-- [**json_editable_document**](../json_editable_document.md) - editable documents of [`json`](../json.md)
-- [**ordered_json_editable_document**](../ordered_json_editable_document.md) - editable documents of
-  [`ordered_json`](../ordered_json.md)
+- [**json_document**](../json_document.md) - documents of the default specialization [`json`](../json.md)
+- [**ordered_json_document**](../ordered_json_document.md) - documents of [`ordered_json`](../ordered_json.md)
 
 ## Member types
 
-- **view_type** - the type of view returned by [`root()`](root.md) (`#!cpp basic_json_view<BasicJsonType, Editable>`)
+- **view_type** - the type of view returned by [`root()`](root.md) (`#!cpp basic_json_view<BasicJsonType>`)
 - **value_t** - the JSON type enumeration, see [`basic_json::value_t`](../basic_json/value_t.md)
-- **image_check** - how [`load()`](load.md) validates an image (`full`, `bounds`, `none`), see [`image_check`](load.md#image_check)
 
 ## Member functions
 
 - [(constructor)](basic_json_document.md)
-
-### Parsing
-
 - [**parse**](parse.md) (_static_) - deserialize from a compatible input, borrowing or owning it as appropriate
 - [**parse_copy**](parse_copy.md) (_static_) - deserialize a copy of a compatible input
 - [**accept**](accept.md) (_static_) - check whether the input is valid JSON
 - [**read**](read.md) - (re-)parse into this document, reusing its memory
-
-### Access
-
 - [**root**](root.md) - the view of the root value
 - [**is_discarded**](is_discarded.md) - return whether the last parse failed
 - [**source**](source.md) - the parsed text
@@ -72,49 +52,6 @@ bookkeeping edits need, and calling any of them on one fails to compile (`#!cpp
 - [**memory_usage**](memory_usage.md) - the number of bytes held by the document
 - [**shrink_to_fit**](shrink_to_fit.md) - release unused index capacity
 
-### Images
-
-- [**save**](save.md) - the document as an image that `load()` reads without parsing
-- [**load**](load.md) (_static_) - read an image written by `save()`
-
-### Edits
-
-- [**set**](set.md) - replace a value, or set an object member, an array element, or the value a JSON pointer refers
-  to (`#!cpp Editable` documents only)
-- [**push_back**](push_back.md) - append to an array (`#!cpp Editable` documents only)
-- [**insert**](insert.md) - insert an element into an array before a given position (`#!cpp Editable` documents only)
-- [**erase**](erase.md) - remove an object member, an array element, or the value a JSON pointer refers to
-  (`#!cpp Editable` documents only)
-
-## Edits
-
-An editable document (`#!cpp Editable == true`) can be changed after parsing, with [`set`](set.md),
-[`push_back`](push_back.md), [`insert`](insert.md), and [`erase`](erase.md);
-[`json_editable_document`](../json_editable_document.md) and
-[`ordered_json_editable_document`](../ordered_json_editable_document.md) are the corresponding specializations. A few
-points apply to every edit:
-
-- **The source text is never written**, and the parsed index never moves: every value keeps the node it was parsed
-  into, so [views](../basic_json_view/index.md) taken before an edit stay valid, including
-  [`root()`](root.md). New values (and the element sequences of an edited array/object) go to storage owned by the
-  document, allocated on demand.
-- **A view keeps referring to the same value.** After [`set`](set.md) replaces the value a view refers to, that view
-  sees the new value; a view of a value that a later edit replaces or drops keeps showing what it last held. An edit
-  of an array or object, however, **invalidates the iterators taken over it** (its members may now live in a
-  different sequence), and a string obtained with [`get_string()`](../basic_json_view/get_string.md) stays valid even
-  as further edits happen (earlier buffers of edited text are kept alive, not overwritten).
-- **Values are accepted three ways:** a [`basic_json_view`](../basic_json_view/index.md) of *any* document
-  (read-only or editable; it is copied, nothing is shared with the source document), a `BasicJsonType` value, or
-  anything `BasicJsonType` can be constructed from (numbers, strings, `#!cpp bool`, `#!cpp nullptr`, containers, ...).
-- [`dump()`](../basic_json_view/dump.md) writes an edited document with members in document order, new members at
-  the end, and, with [`number_format::source`](../basic_json_view/number_format.md), keeps the spelling of every
-  number that was not itself edited -- see [Editing a document](../../features/json_view.md#editing-a-document) for
-  why this matters.
-- [`read()`](read.md) discards all edits, [`shrink_to_fit()`](shrink_to_fit.md) does not move the node index once
-  there are edits, and [`memory_usage()`](memory_usage.md) includes the memory edits use.
-  [`source_offset()`](../basic_json_view/source_offset.md) of a value introduced by an edit is
-  `#!cpp static_cast<std::size_t>(-1)`, the same value it reports for a decoded string.
-
 ## Version history
 
 - Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_document/insert.md

@@ -1,114 +0,0 @@
-# <small>nlohmann::basic_json_document::</small>insert
-
-```cpp
-template<typename I, typename V>
-view_type insert(view_type array, I idx, V&& value);
-```
-
-Only an **editable** document (`#!cpp Editable == true`, e.g. [`json_editable_document`](../json_editable_document.md))
-has `insert`; calling it on a read-only `basic_json_document` fails to compile (`#!cpp static_assert`).
-
-Inserts `value` into `array` as a new element before position `idx`, which must not be past the end
-(`#!cpp idx <= array.size()`; `#!cpp idx == array.size()` appends, like [`push_back`](push_back.md)). Unlike
-[`push_back`](push_back.md), a [null](../basic_json_view/is_null.md) `array` does *not* first become an empty array:
-`array` must already be an array.
-
-`value` is accepted three ways: a [`basic_json_view`](../basic_json_view/index.md) of *any* document -- read-only or
-editable, and it does not have to be `array`'s own document -- which is copied so that nothing is shared with the
-source document afterward; a `BasicJsonType` value; or anything `BasicJsonType` can be constructed from (numbers,
-strings, `#!cpp bool`, `#!cpp nullptr`, containers, ...).
-
-## Template parameters
-
-`I`
-:   an integral type other than `#!cpp bool`, deduced (overloads taking a `#!cpp bool` or a non-integral type for
-    `idx` do not participate in overload resolution).
-
-`V`
-:   the type of `value`, deduced; see above for what is accepted.
-
-## Parameters
-
-`array` (in)
-:   the array to insert into
-
-`idx` (in)
-:   the position to insert `value` before; a negative value throws (see [Exceptions](#exceptions))
-
-`value` (in)
-:   the value to insert
-
-## Return value
-
-a view of the new element, now holding `value`
-
-## Exception safety
-
-Basic exception safety: `value` is fully encoded -- including the checks below -- into storage owned by the document
-before anything already reachable from [`root()`](root.md) is touched, so a failure while encoding `value` (an
-invalid argument, or `#!cpp std::bad_alloc`) leaves the document completely unchanged, other than memory allocated
-for the encoding that is not reclaimed. A failure of a later allocation -- while `array` switches from its parsed
-layout to a growable block, or while that block grows, see [Notes](#notes) -- can still leave `array` already
-switched to that layout even though `value` itself was not inserted.
-
-## Exceptions
-
-Throws [`type_error.309`](../../home/exceptions.md#jsonexceptiontype_error309) if `array` is not an array -- the same
-message [`BasicJsonType::insert`](../basic_json/insert.md) throws for the same type; a null `array` throws this too
-(see above). Throws [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if `idx` is negative,
-or if `#!cpp idx > array.size()`. Throws
-[`invalid_iterator.202`](../../home/exceptions.md#jsonexceptioninvalid_iterator202) ("view does not belong to this
-document") if `array` is a [discarded](../basic_json_view/is_discarded.md) view or a view of a *different* document.
-Throws [`type_error.302`](../../home/exceptions.md#jsonexceptiontype_error302) if `value` is a
-[discarded](../basic_json_view/is_discarded.md) view or a [discarded](../basic_json/is_discarded.md) `BasicJsonType`
-value, and [`type_error.319`](../../home/exceptions.md#jsonexceptiontype_error319) if `value` is (or contains) a
-binary value -- `BasicJsonType` can hold one, but a `json_document` cannot. Throws
-[`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) if `value` is (or contains) a string that is
-not valid UTF-8, with the same message [`BasicJsonType::dump()`](../basic_json/dump.md) gives for that string.
-
-## Complexity
-
-Linear in the number of elements of `array` at or after `idx` (they move one slot over), plus time linear in the
-size of `value` to encode it into the document's storage (constant for a scalar, linear in the number of nested
-values for an array or object): like [`push_back`](push_back.md), the elements of `array` move to a growable block
-of links the first time it is inserted into (or [`set`](set.md)/[`push_back`](push_back.md) on), and that block
-grows in amortized constant time; inserting before the end within that block still shifts every later element.
-
-## Notes
-
-Like [`set`](set.md) on a member or an element, `insert` never moves an existing *element's value* -- only where
-`array`'s *links* to its elements live -- so a view of an existing element of `array` stays valid across an
-`insert`, and keeps referring to the same element even though its index shifts. Any iterator already taken over
-`array` is invalidated, since it was walking the old layout. See [Edits](index.md#edits) for what stays valid across
-an edit in general.
-
-## Examples
-
-??? example
-
-    The example below inserts a step into the middle of a deployment plan, without touching the steps that come
-    after it, and shows that a view taken before the insert keeps referring to the same element even though its
-    index shifts -- something a plain `json`/`ordered_json` array, or its `std::vector`-based storage, has no
-    equivalent for.
-
-    ```cpp
-    --8<-- "examples/basic_json_document__insert.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/basic_json_document__insert.output"
-    ```
-
-## See also
-
-- [push_back](push_back.md) - append to an array
-- [erase](erase.md) - remove an object member, an array element, or the value a JSON pointer refers to
-- [set](set.md) - replace a value, or set an object member, an array element, or the value a JSON pointer refers to
-- [`BasicJsonType::insert`](../basic_json/insert.md) - the corresponding function of `basic_json`
-- [Edits](index.md#edits) - what an edit guarantees, for every overload
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_document/load.md

@@ -1,179 +0,0 @@
-# <small>nlohmann::basic_json_document::</small>load
-
-```cpp
-// (1)
-static basic_json_document load(const std::uint8_t* image, std::size_t size,
-                                 const image_check check = image_check::full);
-
-// (2)
-static basic_json_document load(const std::vector<std::uint8_t>& image,
-                                 const image_check check = image_check::full);
-
-// (3)
-static basic_json_document load(std::vector<std::uint8_t>&& image,
-                                 const image_check check = image_check::full);
-```
-
-1. Reads an image [`save()`](save.md) wrote, from a pointer and a byte count. The image is **borrowed**: `image`
-   must stay alive and unchanged for as long as the returned document, and any view taken from it, is used.
-2. Reads an image from a `#!cpp std::vector`. Also **borrowed** -- equivalent to overload 1 called with
-   `#!cpp image.data()` and `#!cpp image.size()`.
-3. Reads an image, keeping the vector instead of copying it: `image` is moved into the document (no copy), which
-   then owns it for as long as it needs the text and the decoded strings. [`owns_source()`](owns_source.md) is
-   `#!cpp true` afterward.
-
-In every overload, the node index is copied into storage the document itself owns -- so that it is properly aligned,
-and, for an [editable](index.md#edits) document, can be edited -- while the text and the decoded strings stay in
-`image`. The hash indexes [large objects](../../features/json_view.md) use for lookup are rebuilt, exactly as after
-parsing.
-
-## Parameters
-
-`image` (in)
-:   the image [`save()`](save.md) wrote (overloads 1 and 2), or one to take ownership of (overload 3)
-
-`size` (in)
-:   the number of bytes at `image` (overload 1)
-
-`check` (in)
-:   how thoroughly to validate `image` before trusting it; see [`image_check`](#image_check) below (optional,
-    `#!cpp image_check::full` by default)
-
-## Return value
-
-The document read from the image.
-
-## Exception safety
-
-Overloads 1 and 2 give the strong guarantee: `image` is only read, never written, so a thrown exception leaves the
-caller's buffer untouched.
-
-Overload 3 moves `image` into the document *before* validating it, so that a good image is kept without a copy. If
-loading then fails, the partially built document -- and the vector now inside it -- is discarded along with the
-exception, and `image` itself is left **empty**, not restored to what was passed in. Move a copy in instead, or
-validate with overload 2 first, if the original vector must survive a failed load.
-
-## Exceptions
-
-On a big-endian target, throws [`type_error.320`](../../home/exceptions.md#jsonexceptiontype_error320) -- the same
-exception [`save()`](save.md#exceptions) throws there, since the image format is little-endian only.
-
-Otherwise throws [`parse_error.116`](../../home/exceptions.md#jsonexceptionparse_error116) if `image` is not one
-`save()` could have written, or fails the requested `check`:
-
-| message               | when                                                                                                |
-|------------------------|------------------------------------------------------------------------------------------------------|
-| `too short`            | `image` is `#!cpp nullptr`, or `size` is smaller than the 64-byte header                             |
-| `unknown format`       | the header's magic bytes or version do not match, or a reserved header field is not zero             |
-| `sizes out of range`   | the node count, text size, or decoded-string size the header describes does not fit `size`, or the `#!cpp '\0'` after the text or after the decoded strings is missing |
-| `the check failed`     | `check` is not `#!cpp image_check::none`, and the image fails it -- see [`image_check`](#image_check) |
-
-!!! failure "Example messages"
-
-    ```
-    [json.exception.parse_error.116] parse error: invalid json_document image: too short
-    ```
-    ```
-    [json.exception.parse_error.116] parse error: invalid json_document image: unknown format
-    ```
-    ```
-    [json.exception.parse_error.116] parse error: invalid json_document image: sizes out of range
-    ```
-    ```
-    [json.exception.parse_error.116] parse error: invalid json_document image: the check failed
-    ```
-
-## Complexity
-
-Linear in the number of nodes, which are always copied into the document. `#!cpp image_check::none` does not read
-the text or the decoded strings. `#!cpp image_check::bounds` reads one byte of the text for each float token (its sign,
-to check the recorded digits against the token's length), and nothing else of the text or the decoded strings.
-
-With `#!cpp image_check::full`, linear in the size of the image (the nodes, the text, and the decoded strings), plus
-sorting the ranges of the strings and of the float tokens (at most one per node): the contents of each distinct range
-are checked once, however many nodes refer to it.
-
-## Notes
-
-### `image_check` { #image_check }
-
-```cpp
-using image_check = detail::view::image_check;
-
-enum class image_check
-{
-    full,
-    bounds,
-    none
-};
-```
-
-How thoroughly `load()` validates `image` before trusting it.
-
-`full` (the default)
-:   Checks everything the parser itself guarantees: structure and bounds; that every string is valid UTF-8 (and, for a
-    string still in the source text, that it contains no quote, backslash, or control character); and that every number
-    token is well-formed and matches the value stored for it. Strings and float tokens may share a range only if the
-    ranges are identical (as nodes that share a value do), and never overlap otherwise. Reading and serializing a
-    checked image is safe and always produces valid JSON, exactly as for a parsed document. This is the right choice for
-    an image from anything you do not fully control -- a file, a cache shared with other processes, a peer on the
-    network.
-
-`bounds`
-:   Checks structure and bounds only: that every offset and count in the node index stays inside the image. So
-    `load()`, [`root()`](root.md), element access, and [`materialize()`](../basic_json_view/materialize.md) can never
-    read outside the image, even on a damaged one. It does *not* guarantee that the image describes valid JSON: a
-    string that a `full` check would have rejected can make [`dump()`](../basic_json_view/dump.md) write invalid UTF-8
-    or invalid JSON, or throw [`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316), and a number can
-    read back with a value that does not match how it is spelled. An [editable document](../json_editable_document.md)
-    does not take such a string over: [`set`](set.md), [`push_back`](push_back.md) and [`insert`](insert.md) throw
-    `type_error.316` when they copy it from a view of the loaded document, and leave the editable document unchanged.
-    `bounds` skips scanning the text and the decoded strings, so it fits a cache your own process just wrote and reads
-    straight back, where damage would mean a bug or a hardware fault rather than adversarial input.
-
-`none`
-:   Checks nothing. Reading a damaged image is undefined behavior, so use it only for an image you trust as much as
-    your own memory.
-
-**Lifetime.** Overloads 1 and 2 borrow `image`: it must stay alive and byte-for-byte unchanged for as long as the
-returned document, and any [view](../basic_json_view/index.md) taken from it, is used -- exactly like a document
-[`parse()`](parse.md) borrowed its input for. Overload 3 avoids this by keeping the vector itself; see
-[`owns_source`](owns_source.md).
-
-!!! warning "Experimental"
-
-    The image format is versioned but not yet stable, and may change in an incompatible way before it is declared
-    stable; `load()` already rejects an image written by a different format version with `parse_error.116`
-    ("unknown format"). Use images to cache a document within one build of the library, or to hand one to another
-    process running the *same* build on the *same* (little-endian) machine -- not as a long-term storage format.
-
-## Examples
-
-??? example "Caching a document, ownership, and a rejected image"
-
-    The example below saves a parsed document as an image, checks that `load()` reproduces the original
-    [`dump()`](../basic_json_view/dump.md) without parsing, and shows the difference between
-    `load(std::move(image))` (owned) and `load(image)` (borrowed). It then damages one byte of the image and shows
-    `image_check::full` rejecting it with `parse_error.116`, while `image_check::bounds` -- meant for a cache the
-    process already trusts -- still reads it without going out of bounds.
-
-    ```cpp
-    --8<-- "examples/basic_json_document__load.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/basic_json_document__load.output"
-    ```
-
-## See also
-
-- [save](save.md) - write the document as an image
-- [owns_source](owns_source.md) - return whether the document holds its own copy of the text
-- [parse](parse.md) - deserialize from JSON text instead of an image
-- [Images](../../features/json_view.md#images) - why and when to use images
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_document/parse.md

@@ -149,7 +149,6 @@ buffer of a given length, pass a pair of pointers: `#!cpp parse(ptr, ptr + len)`
 - [accept](accept.md) - check whether the input is valid JSON
 - [read](read.md) - (re-)parse into this document, reusing its memory
 - [owns_source](owns_source.md) - return whether the document holds its own copy of the text
-- [load](load.md) - read a document from an image instead of parsing JSON text
 - [`BasicJsonType::parse`](../basic_json/parse.md) - the corresponding function of `basic_json`
 
 ## Version history

docs/mkdocs/docs/api/basic_json_document/push_back.md

@@ -1,102 +0,0 @@
-# <small>nlohmann::basic_json_document::</small>push_back
-
-```cpp
-template<typename V>
-view_type push_back(view_type array, V&& value);
-```
-
-Appends `value` as a new last element of `array`. A [null](../basic_json_view/is_null.md) `array` first becomes an
-empty array, the same way [`set`](set.md) turns a null `object` into an empty object.
-
-`value` is accepted three ways: a [`basic_json_view`](../basic_json_view/index.md) of *any* document -- read-only or
-editable, and it does not have to be `array`'s own document -- which is copied so that nothing is shared with the
-source document afterward; a `BasicJsonType` value; or anything `BasicJsonType` can be constructed from (numbers,
-strings, `#!cpp bool`, `#!cpp nullptr`, containers, ...).
-
-Only an **editable** document (`#!cpp Editable == true`, e.g. [`json_editable_document`](../json_editable_document.md))
-has `push_back`; calling it on a read-only `basic_json_document` fails to compile (`#!cpp static_assert`).
-
-## Template parameters
-
-`V`
-:   the type of `value`, deduced; see above for what is accepted.
-
-## Parameters
-
-`array` (in)
-:   the array (or null value) to append to
-
-`value` (in)
-:   the value to append
-
-## Return value
-
-a view of the new last element of `array`, now holding `value`
-
-## Exception safety
-
-Basic exception safety: `value` is fully encoded -- including the checks below -- into storage owned by the document
-before anything already reachable from [`root()`](root.md) is touched, so a failure while encoding `value` (an
-invalid argument, or `#!cpp std::bad_alloc`) leaves the document completely unchanged, other than memory allocated
-for the encoding that is not reclaimed. A failure of a later allocation -- while `array` switches from its parsed
-layout to a growable block, or while that block grows, see [Notes](#notes) -- can still leave a partial effect, such
-as a null `array` argument already turned into an empty array even though `value` itself was not appended.
-
-## Exceptions
-
-Throws [`type_error.308`](../../home/exceptions.md#jsonexceptiontype_error308) if `array` is neither an array nor
-null -- the same message [`BasicJsonType::push_back`](../basic_json/push_back.md) throws for the same type. Throws
-[`invalid_iterator.202`](../../home/exceptions.md#jsonexceptioninvalid_iterator202) ("view does not belong to this
-document") if `array` is a [discarded](../basic_json_view/is_discarded.md) view or a view of a *different* document.
-Throws [`type_error.302`](../../home/exceptions.md#jsonexceptiontype_error302) if `value` is a
-[discarded](../basic_json_view/is_discarded.md) view or a [discarded](../basic_json/is_discarded.md) `BasicJsonType`
-value, and [`type_error.319`](../../home/exceptions.md#jsonexceptiontype_error319) if `value` is (or contains) a
-binary value -- `BasicJsonType` can hold one, but a `json_document` cannot. Throws
-[`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) if `value` is (or contains) a string that is
-not valid UTF-8, with the same message [`BasicJsonType::dump()`](../basic_json/dump.md) gives for that string.
-
-## Complexity
-
-Amortized constant, plus time linear in the size of `value` to encode it into the document's storage (constant for
-a scalar, linear in the number of nested values for an array or object): the elements of `array` move to a growable
-block of links the first time it is appended to (or [`set`](set.md) on), and that block itself grows -- doubling its
-capacity, so the cost of growing it amortizes to constant per element -- only once it runs out of room. See
-[Notes](#notes).
-
-## Notes
-
-Like [`set`](set.md) on a member or an element, `push_back` never moves an existing element itself -- only where
-`array`'s *links* to its elements live -- so a view of an existing element of `array` stays valid across a
-`push_back`, but any iterator already taken over `array` is invalidated, since it was walking the old layout. See
-[Edits](index.md#edits) for what stays valid across an edit in general.
-
-## Examples
-
-??? example
-
-    The example below appends records to an array one at a time, as they might arrive from a stream of events,
-    without ever building a `BasicJsonType` value for the array or for the records already in it, and shows that a
-    view taken from an earlier `push_back` still refers to the same element once later ones have run.
-
-    ```cpp
-    --8<-- "examples/basic_json_document__push_back.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/basic_json_document__push_back.output"
-    ```
-
-## See also
-
-- [set](set.md) - replace a value, or set an object member, an array element, or the value a JSON pointer refers to
-- [insert](insert.md) - insert an element into an array before a given position
-- [erase](erase.md) - remove an object member, an array element, or the value a JSON pointer refers to
-- [root](root.md) - the view of the root value
-- [`BasicJsonType::push_back`](../basic_json/push_back.md) - the corresponding function of `basic_json`
-- [Edits](index.md#edits) - what an edit guarantees, for every overload
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_document/read.md

@@ -51,11 +51,6 @@ own on the next, since ownership is decided freshly each time. An input that is
 [`parse()`](parse.md#notes)) is written into the document's previous owned copy, reusing its memory; a moved-in
 `#!cpp std::string` replaces it.
 
-Reusing a document matters most for large inputs: the operating system provides the memory of a fresh node index one
-page at a time, and every page costs a page fault the first time it is written. On x86-64 Linux (4 KiB pages), parsing
-a 55 MB document into a reused document took about 40 % less time than parsing it into a fresh one. Programs that parse
-many documents of similar size should therefore keep one document and call `read()`.
-
 An integer argument that is not a `#!cpp bool` where the flags are expected, such as `#!cpp read(ptr, len)`, does not
 compile; see [`parse`](parse.md#notes).
 
@@ -80,7 +75,6 @@ compile; see [`parse`](parse.md#notes).
 
 - [parse](parse.md) - deserialize from a compatible input
 - [root](root.md) - the view of the root value
-- [load](load.md) - read a document from an image instead of parsing JSON text
 
 ## Version history
 

docs/mkdocs/docs/api/basic_json_document/save.md

@@ -1,104 +0,0 @@
-# <small>nlohmann::basic_json_document::</small>save
-
-```cpp
-std::vector<std::uint8_t> save() const;
-```
-
-Writes the document as an *image*: a byte buffer that [`load`](load.md) reads back without parsing. The image holds
-the node index, the source text (plus, for an edited document, the number tokens edits wrote), and the decoded
-strings (plus the strings edits wrote) -- everything [`root()`](root.md) needs, with nothing left to parse.
-
-An edited document is written in its *current* state, with its values in document order, the way the library's own
-parser would have produced them for that JSON text: a member [`set`](set.md) added goes at the end, an
-[`erase`](erase.md)d member leaves no trace, and a float that is not finite (NaN or positive/negative infinity)
-becomes null, the same substitution [`dump()`](../basic_json_view/dump.md) makes. The same document always saves to
-the same bytes -- also across `BasicJsonType` and `#!cpp Editable`, since the image reflects document order and
-values only, not which specialization produced them.
-
-## Return value
-
-The image, as a `#!cpp std::vector<std::uint8_t>`. Pass it, or a pointer to its data together with its size, to
-[`load`](load.md) to read the document back.
-
-## Exception safety
-
-Strong guarantee: `save()` does not modify `#!cpp *this` (it is `#!cpp const`), so if it throws, the document is left
-exactly as it was, and the partially built image is discarded with the exception.
-
-## Exceptions
-
-Throws [`type_error.320`](../../home/exceptions.md#jsonexceptiontype_error320) if the document is
-[discarded](is_discarded.md) -- a default-constructed document, or one a failed [`parse()`](parse.md)/
-[`read()`](read.md) with `allow_exceptions == false` left discarded.
-
-On a big-endian target, throws `type_error.320` with a different message instead: the image format is little-endian
-only (see [Notes](#notes)).
-
-Throws [`out_of_range.416`](../../home/exceptions.md#jsonexceptionout_of_range416) if the node count, the text, or
-the decoded strings of the image would individually reach 4 GiB -- the same 32-bit offsets
-[`parse()`](parse.md#exceptions) and, for edits, [`set`](set.md)/[`push_back`](push_back.md) are already limited to.
-
-!!! failure "Example messages"
-
-    ```
-    [json.exception.type_error.320] cannot save a discarded json_document
-    ```
-    ```
-    [json.exception.type_error.320] json_document images need a little-endian target
-    ```
-    ```
-    [json.exception.out_of_range.416] images of 4 GiB or more are not supported by json_document
-    ```
-
-## Complexity
-
-Linear in the size of the document: the number of nodes, plus the length of the text and the decoded strings that end
-up in the image.
-
-## Notes
-
-**Format.** The image begins with a 64-byte header (the magic bytes `#!cpp "NJVI"`, a version number, the node count,
-and the sizes of the text and the decoded strings, all little-endian), followed by the nodes
-([16 bytes each](../../home/architecture.md#node-index-of-json-views)), the text and a `#!cpp '\0'`, and the decoded
-strings and a `#!cpp '\0'`. [`load`](load.md) checks the header, and the sizes it describes, before reading anything
-else -- see [`load`'s Exceptions](load.md#exceptions).
-
-!!! warning "Experimental"
-
-    The image format is versioned but not yet stable: it may change in an incompatible way before it is declared
-    stable. Use images to cache a document within one build of the library, or to hand one to another process running
-    the *same* build on the *same* (little-endian) machine -- not as a long-term storage format. Keep the original
-    JSON text if you need to read a saved document back with a future library version.
-
-**Little-endian only.** The image is written as raw little-endian bytes, with no byte-swapping. `save()` (and
-[`load`](load.md)) throw `type_error.320` on a big-endian target rather than silently produce bytes a big-endian
-reader could not interpret correctly.
-
-## Examples
-
-??? example "Caching a parsed document as an image"
-
-    The example below saves a parsed configuration as an image -- the way a service might cache one to answer later
-    requests without parsing the text again -- and confirms that loading it back gives exactly the same result as
-    parsing did, and that saving is deterministic.
-
-    ```cpp
-    --8<-- "examples/basic_json_document__save.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/basic_json_document__save.output"
-    ```
-
-## See also
-
-- [load](load.md) - read an image written by `save()`
-- [owns_source](owns_source.md) - return whether the document holds its own copy of the text
-- [`basic_json_view::dump`](../basic_json_view/dump.md) - serialize the document to JSON text instead of an image
-- [Images](../../features/json_view.md#images) - why and when to use images
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_document/set.md

@@ -1,203 +0,0 @@
-# <small>nlohmann::basic_json_document::</small>set
-
-```cpp
-// (1)
-template<typename V>
-view_type set(view_type target, V&& value);
-
-// (2)
-template<typename V>
-view_type set(view_type object, string_view_t key, V&& value);
-
-// (3)
-template<typename I, typename V>
-view_type set(view_type array, I idx, V&& value);
-
-// (4)
-template<typename V>
-view_type set(const json_pointer& ptr, V&& value);
-```
-
-Only an **editable** document (`#!cpp Editable == true`, e.g. [`json_editable_document`](../json_editable_document.md))
-has `set`; calling it on a read-only `basic_json_document` fails to compile (`#!cpp static_assert`).
-
-1. Replaces the value `target` refers to with `value`.
-2. Sets the member `key` of the object `object` to `value`: assigns it if `object` already has a member with this
-   key -- the first one, should the key occur more than once, and the later duplicates are then dropped (see the
-   [Notes](#notes) below) -- or appends a new member at the end otherwise. A [null](../basic_json_view/is_null.md)
-   `object` first becomes an empty object.
-3. Assigns `value` to the element at index `idx` of the array `array`, which must already exist (`#!cpp idx <
-   array.size()`).
-4. Sets the value the JSON pointer `ptr` refers to, relative to [`root()`](root.md), to `value`. The *parent* of the
-   target must already exist: an object member is set as in 2. (added if it does not exist yet), an array element is
-   assigned as in 3., and a last reference token of `#!cpp "-"`, or equal to the size of the array, appends `value`
-   instead, exactly as [`push_back`](push_back.md) would. A [null](../basic_json_view/is_null.md) parent becomes what
-   [`basic_json::operator[]`](../basic_json/operator%5B%5D.md) with a JSON pointer makes of it: an array if the last
-   reference token is `#!cpp "-"` or consists of digits only (for an index beyond 0, the array is first filled with
-   null values up to that index), an object otherwise. An empty `ptr` sets [`root()`](root.md) itself, as in 1.
-
-In every overload, `value` is accepted three ways: a [`basic_json_view`](../basic_json_view/index.md) of *any*
-document -- read-only or editable, and it does not have to be `target`'s/`object`'s/`array`'s own document -- which
-is copied so that nothing is shared with the source document afterward; a `BasicJsonType` value; or anything
-`BasicJsonType` can be constructed from (numbers, strings, `#!cpp bool`, `#!cpp nullptr`, containers, ...).
-
-## Template parameters
-
-`V`
-:   the type of `value`, deduced; see above for what is accepted.
-
-`I`
-:   an integral type other than `#!cpp bool`, deduced (overloads taking a `#!cpp bool` or a non-integral type for
-    `idx` do not participate in overload resolution).
-
-## Parameters
-
-`target` (in)
-:   the value to replace
-
-`object` (in)
-:   the object (or null value) whose member to set
-
-`array` (in)
-:   the array whose element to assign
-
-`key` (in)
-:   the key of the member to set
-
-`idx` (in)
-:   the index of the element to assign; a negative value throws (see [Exceptions](#exceptions))
-
-`ptr` (in)
-:   a JSON pointer to the value to set, relative to `root()`
-
-`value` (in)
-:   the new value
-
-## Return value
-
-1. a view of `target`, now holding `value`
-2. a view of the member `key` of `object`, now holding `value`
-3. a view of the element `idx` of `array`, now holding `value`
-4. a view of the value `ptr` refers to, now holding `value`
-
-## Exception safety
-
-Basic exception safety: `value` is fully encoded -- including the checks below -- into storage owned by the document
-before anything already reachable from [`root()`](root.md) is touched, so a failure while encoding `value` (an
-invalid argument, or `#!cpp std::bad_alloc`) leaves the document completely unchanged, other than memory allocated
-for the encoding that is not reclaimed. A failure of a later allocation -- while an edited array or object switches
-from its parsed layout to a growable block, see [Notes](#notes) -- can still leave a partial effect, such as a
-[null](../basic_json_view/is_null.md) `object`/`array` argument already turned into an empty object/array even
-though `value` itself was not linked in. Likewise, a failure of `value` in 4. leaves a null parent that is set with an
-index beyond 0 already filled with the null values before the index.
-
-## Exceptions
-
-1. Throws [`type_error.302`](../../home/exceptions.md#jsonexceptiontype_error302) if `value` is a
-   [discarded](../basic_json_view/is_discarded.md) view, or a [discarded](../basic_json/is_discarded.md)
-   `BasicJsonType` value (e.g. `#!cpp BasicJsonType(value_t::discarded)`) -- an object or array `value`, of either
-   kind, is fine and is encoded as a whole subtree.
-2. Throws [`type_error.305`](../../home/exceptions.md#jsonexceptiontype_error305) if `object` is neither an object
-   nor null -- the same message [`operator[]`](../basic_json_view/operator%5B%5D.md) throws for a string argument on
-   such a value. Throws [`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) if `key` is not
-   valid UTF-8, with the same message [`BasicJsonType::dump()`](../basic_json/dump.md) gives for that string.
-   Also throws what 1. throws for `value`.
-3. Throws `type_error.305` if `array` is not an array -- the same message `operator[]` throws for a numeric argument
-   on such a value. Throws [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if `idx` is
-   negative, or if `#!cpp idx >= array.size()`. Also throws what 1. throws for `value`.
-4. Throws what [`at`](../basic_json_view/at.md) throws (overload 3) for resolving `ptr`'s parent, except that a
-   missing object member or an array index equal to the array's size at the very last reference token is not an
-   error there (it becomes a new member or an appended element) instead of
-   [`out_of_range.403`](../../home/exceptions.md#jsonexceptionout_of_range403)/[`out_of_range.402`](../../home/exceptions.md#jsonexceptionout_of_range402).
-   For the last reference token itself: if the parent is an object (or a primitive value, where it throws
-   `type_error.305`), throws what 2. throws; if the parent is an array, throws what 3. throws for an index that is
-   out of range, or, for a token that is not a valid array index,
-   [`parse_error.106`](../../home/exceptions.md#jsonexceptionparse_error106) (a leading `#!cpp '0'`),
-   [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) (not a number),
-   [`out_of_range.410`](../../home/exceptions.md#jsonexceptionout_of_range410) (too large for `size_type`), or
-   [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) (an empty token); the same errors are
-   thrown for a null parent and a token of digits (the parent is not changed then), and
-   [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if the index is 4294967295 or more.
-   Also throws what 1. throws for `value`.
-
-Every overload also throws [`type_error.319`](../../home/exceptions.md#jsonexceptiontype_error319) if `value` is (or
-contains) a binary value -- `BasicJsonType` can hold one, but a `json_document` cannot -- and
-[`invalid_iterator.202`](../../home/exceptions.md#jsonexceptioninvalid_iterator202) ("view does not belong to this
-document") if `target`/`object`/`array` is a [discarded](../basic_json_view/is_discarded.md) view or a view of a
-*different* document (overloads 1-3 only; overload 4 always starts from this document's own [`root()`](root.md)).
-
-## Complexity
-
-1. Linear in the size of `value` (encoding it into the document's storage): constant for a scalar, linear in the
-   number of nested values for an array or object. If `target` is itself an array or object that spans more than one
-   node in its parent's original, unedited layout, and `value` is a scalar, replacing it additionally costs time
-   linear in the size of the document, the *first* time (the parent of `target` is looked up from
-   [`root()`](root.md), and then switches to links) -- see [Notes](#notes). Once the parent has links, `target` is
-   replaced in constant time: setting every element of a large array one after the other is linear overall. To avoid
-   the lookup altogether, use 3. (or 2. for an object), which know the parent.
-2. Linear in the number of members of `object`, to find an existing member with `key`, plus the complexity of 1. for
-   `value`.
-3. Constant, plus the complexity of 1. for `value`.
-4. Linear in the number of reference tokens of `ptr` and, for each token, in the number of members of the object at
-   that level or the index into the array (as [`at`](../basic_json_view/at.md)), plus the complexity of 2. or 3. for
-   the last token; for a null parent and an index, linear in the index.
-
-## Notes
-
-!!! info "Duplicate keys"
-
-    If `object` already has more than one member with `key` (2.), the *first* one is assigned `value` and every
-    later member with the same key is removed -- so that a lookup, an iteration, and
-    [`materialize()`](../basic_json_view/materialize.md) of `object` afterward all agree on a single value for
-    `key`, the same way [`operator[]`](../basic_json_view/operator%5B%5D.md) already picks the first occurrence of a
-    duplicate key for reading. See the [Notes on duplicate keys](../basic_json_view/operator%5B%5D.md#notes) of
-    `operator[]`.
-
-Setting a member (2.) or an element (3., through 4.) of an array or object whose elements have not been edited
-before switches it from its parsed layout to a growable block holding links to its elements; a later
-[`push_back`](push_back.md) or `set` on the same container reuses that block, growing it (amortized constant time)
-only once it runs out of room. This never moves an element itself -- only where the container's *links* to its
-elements live -- so a view of an element stays valid, but any iterator already taken over the container is
-invalidated, since it was walking the old layout. See [Edits](index.md#edits) for what stays valid across an edit in
-general.
-
-The same switch happens, for the same reason, when overload 1. replaces a multi-node array/object value with a
-scalar: the *parent's* element sequence is what has to switch to links, not `target` itself, because the parent
-originally stepped over `target`'s whole subtree by its node count, which no longer applies once `target` is a
-one-node scalar.
-
-## Examples
-
-??? example "Example: (1)/(2)/(3)/(4) replace a value, set a member, assign an element, set via a JSON pointer"
-
-    The example below edits a small configuration document -- replacing a value, adding an object member, assigning
-    an array element, and reaching a field through a JSON pointer -- and shows what
-    [`dump()`](../basic_json_view/dump.md) preserves that is lost once the same edits are made on a `BasicJsonType`
-    value instead: the order object members were written in, and the exact spelling of a number that was never
-    touched.
-
-    ```cpp
-    --8<-- "examples/basic_json_document__set.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/basic_json_document__set.output"
-    ```
-
-## See also
-
-- [push_back](push_back.md) - append to an array
-- [insert](insert.md) - insert an element into an array
-- [erase](erase.md) - remove an object member, an array element, or the value a JSON pointer refers to
-- [root](root.md) - the view of the root value, the starting point of overload 4
-- [`basic_json_view::dump`](../basic_json_view/dump.md) - serialize the document, keeping an untouched number's
-  spelling with `#!cpp number_format::source`
-- [Edits](index.md#edits) - what an edit guarantees, for every overload
-- [Editing a document](../../features/json_view.md#editing-a-document) - why editable documents keep the source
-  text's order and number spelling
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/basic_json_view/at.md

@@ -77,8 +77,6 @@ None of these exceptions carry a [`JSON_DIAGNOSTICS`](../macros/json_diagnostics
 1. Linear in the number of members: as for [`ordered_json`](../ordered_json.md), members are compared one after
    another, in document order, stopping at the first match. Each comparison first checks the
    key's length -- already known from the index, without reading the key bytes -- before comparing its content.
-   Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes
-   constant time on average.
 2. Linear in `idx`: elements are skipped one at a time from the first one, since they are not a fixed size in the
    index (unlike `BasicJsonType`'s array, which is random-access).
 3. Linear in the number of reference tokens of `ptr` and, for each token, in the number of members of the object at

docs/mkdocs/docs/api/basic_json_view/contains.md

@@ -35,8 +35,6 @@ No-throw guarantee: this function never throws exceptions.
 1. Linear in the number of members: as for [`ordered_json`](../ordered_json.md), members are compared one after
    another, in document order, stopping at the first match. Each comparison first checks the
    key's length -- already known from the index, without reading the key bytes -- before comparing its content.
-   Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes
-   constant time on average.
 2. Linear in the number of reference tokens of `ptr` and, for each token, in the number of members of the object at
    that level or the index into the array -- as for [`operator[]`](operator[].md#complexity) and
    [`at`](at.md#complexity) with a JSON pointer.

docs/mkdocs/docs/api/basic_json_view/count.md

@@ -28,8 +28,7 @@ No-throw guarantee: this function never throws exceptions.
 Linear in the number of members: unlike the lookup functions, `count()` does not stop at the first match, because it
 has to count every member with the key. Members are compared one after another, in document order. Each comparison
 first checks the key's length -- already known from the index, without reading the key bytes -- before comparing its
-content. The hash index of the keys of objects with 128 or more members does not help here, since every member
-is visited.
+content.
 
 ## Notes
 

docs/mkdocs/docs/api/basic_json_view/find.md

@@ -28,8 +28,6 @@ No-throw guarantee: this function never throws exceptions.
 Linear in the number of members: as for [`ordered_json`](../ordered_json.md), members are compared one after another,
 in document order, stopping at the first match. Each comparison first checks the key's length
 -- already known from the index, without reading the key bytes -- before comparing its content.
-Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes
-constant time on average.
 
 ## Notes
 

docs/mkdocs/docs/api/basic_json_view/index.md

@@ -3,7 +3,7 @@
 <small>Defined in header `<nlohmann/json_view.hpp>`</small>
 
 ```cpp
-template<typename BasicJsonType, bool Editable = false>
+template<typename BasicJsonType>
 class basic_json_view;
 ```
 
@@ -36,30 +36,16 @@ Moving the document itself does not invalidate its views: the index is heap-allo
 [`json_pointer`](../json_pointer/index.md). Unlike `basic_json`, there are no implicit conversion operators (no
 `#!cpp operator ValueType()`), and no `#!cpp get_ptr()` or `#!cpp get_ref()`; see [`get`](get.md).
 
-`basic_json_view` itself is always read-only -- it never has a `set` or `push_back` of its own. A view of an
-**editable** document (`#!cpp Editable == true`) sees every edit made through
-[`basic_json_document::set`](../basic_json_document/set.md) and
-[`basic_json_document::push_back`](../basic_json_document/push_back.md): once a value is changed, every view that
-still refers to it -- including ones taken before the change -- reads the new value. See
-[Edits](../basic_json_document/index.md#edits).
-
 ## Template parameters
 
 `BasicJsonType`
 :   a specialization of [`basic_json`](../basic_json/index.md), matching the
     [`basic_json_document`](../basic_json_document/index.md) the view was taken from.
 
-`Editable`
-:   whether the view is of an editable document, matching the [`basic_json_document`](../basic_json_document/index.md)
-    it was taken from (optional, `#!cpp false` by default). See [Edits](../basic_json_document/index.md#edits).
-
 ## Specializations
 
 - [**json_view**](../json_view.md) - views of a [`json_document`](../json_document.md)
 - [**ordered_json_view**](../ordered_json_view.md) - views of an [`ordered_json_document`](../ordered_json_document.md)
-- [**json_editable_view**](../json_editable_view.md) - views of a [`json_editable_document`](../json_editable_document.md)
-- [**ordered_json_editable_view**](../ordered_json_editable_view.md) - views of an
-  [`ordered_json_editable_document`](../ordered_json_editable_document.md)
 
 ## Member types
 

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

@@ -83,8 +83,6 @@ None of these exceptions carry a [`JSON_DIAGNOSTICS`](../macros/json_diagnostics
    another, in document order, stopping at the first match. Each comparison first checks the
    key's length -- already known from the index, without reading the key bytes -- before comparing its content, so a
    key of a different length than `key` is rejected without touching the source text.
-   Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes
-   constant time on average.
 2. Linear in `idx`: elements are skipped one at a time from the first one, since they are not a fixed size in the
    index (unlike `BasicJsonType`'s array, which is random-access).
 3. Linear in the number of reference tokens of `ptr` and, for each token, in the number of members of the object at
@@ -116,7 +114,6 @@ document.
     member in order and so keep the *last* value for a repeated key, so `#!cpp v["a"]` and
     `#!cpp v.materialize()["a"]` can differ. To get the value `parse()` would give, use
     [`materialize()`](materialize.md) or iterate the members with [`items()`](items.md) and keep the last match.
-    The key hash index of a larger object (128 members or more) leads to the first member of a key as well.
     [`begin()`](begin.md)/[`end()`](end.md) and [`items()`](items.md) iterate over *all* members, including
     duplicates, in document order. See [Duplicate keys](../../features/json_view.md#duplicate-keys) and
     [`size()`](size.md#notes).

docs/mkdocs/docs/api/basic_json_view/value.md

@@ -70,8 +70,6 @@ None of these exceptions carry a [`JSON_DIAGNOSTICS`](../macros/json_diagnostics
 1. Linear in the number of members: as for [`operator[]`](operator[].md#complexity), members are compared one after
    another, in document order, stopping at the first match. Plus the complexity of converting
    the found member to `T` (see [`get`](get.md)).
-   Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes
-   constant time on average.
 2. Linear in the number of reference tokens of `ptr` and, for each token, in the number of members of the object at
    that level or the index into the array -- as for the [`operator[]`](operator[].md#complexity) and
    [`at`](at.md#complexity) overloads that take a JSON pointer. Plus the complexity of converting the resolved value

docs/mkdocs/docs/api/byte_container_with_subtype/container_type.md

@@ -1,32 +0,0 @@
-# <small>nlohmann::byte_container_with_subtype::</small>container_type
-
-```cpp
-using container_type = BinaryType;
-```
-
-The type of the underlying binary container, forwarded from the `BinaryType` template parameter that
-`byte_container_with_subtype` is instantiated with. `byte_container_with_subtype` publicly inherits from
-`container_type`.
-
-See [`basic_json::binary_t`](../basic_json/binary_t.md) for the type typically used to instantiate
-`BinaryType`.
-
-## Examples
-
-??? example
-
-    The example shows the type `container_type`.
-
-    ```cpp
-    --8<-- "examples/byte_container_with_subtype__container_type.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/byte_container_with_subtype__container_type.output"
-    ```
-
-## Version history
-
-- Since version 3.8.0.

docs/mkdocs/docs/api/byte_container_with_subtype/subtype_type.md

@@ -1,28 +0,0 @@
-# <small>nlohmann::byte_container_with_subtype::</small>subtype_type
-
-```cpp
-using subtype_type = std::uint64_t;
-```
-
-The type used to store the optional binary subtype tag. See [`subtype`](subtype.md) and
-[`set_subtype`](set_subtype.md).
-
-## Examples
-
-??? example
-
-    The example shows the type `subtype_type`.
-
-    ```cpp
-    --8<-- "examples/byte_container_with_subtype__subtype_type.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/byte_container_with_subtype__subtype_type.output"
-    ```
-
-## Version history
-
-- Since version 3.8.0.

docs/mkdocs/docs/api/json_editable_document.md

@@ -1,43 +0,0 @@
-# <small>nlohmann::</small>json_editable_document
-
-<small>Defined in header `<nlohmann/json_view.hpp>`</small>
-
-```cpp
-using json_editable_document = basic_json_document<json, true>;
-```
-
-This type is an **editable** [`basic_json_document`](basic_json_document/index.md) of the default
-[`json`](json.md) specialization: in addition to everything [`json_document`](json_document.md) offers,
-[`set`](basic_json_document/set.md) and [`push_back`](basic_json_document/push_back.md) change values after
-parsing, without ever rewriting the source text -- see [Edits](basic_json_document/index.md#edits) and
-[Editing a document](../features/json_view.md#editing-a-document).
-
-## Examples
-
-??? example
-
-    The example below patches two fields of a small configuration document -- changing one and adding another --
-    and dumps it back out with the member order and the spelling of the untouched number preserved, something a
-    plain [`json`](json.md) value cannot do.
-
-    ```cpp
-    --8<-- "examples/json_editable_document.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/json_editable_document.output"
-    ```
-
-## See also
-
-- [json_editable_view](json_editable_view.md) - a view of a value of a `json_editable_document`
-- [json_document](json_document.md) - the read-only document this type adds edits to
-- [ordered_json_editable_document](ordered_json_editable_document.md) - the corresponding editable document for
-  `ordered_json`
-- [Edits](basic_json_document/index.md#edits) - what an edit guarantees
-
-## Version history
-
-Since version 3.13.0.

docs/mkdocs/docs/api/json_editable_view.md

@@ -1,41 +0,0 @@
-# <small>nlohmann::</small>json_editable_view
-
-<small>Defined in header `<nlohmann/json_view.hpp>`</small>
-
-```cpp
-using json_editable_view = basic_json_view<json, true>;
-```
-
-This type is a [`basic_json_view`](basic_json_view/index.md) of a value of a
-[`json_editable_document`](json_editable_document.md). It offers the same read-only interface as
-[`json_view`](json_view.md); what is different is what it can be a view *of* -- a value that
-[`set`](basic_json_document/set.md) and [`push_back`](basic_json_document/push_back.md) can change, with every view
-still referring to it seeing the change, see [Edits](basic_json_document/index.md#edits).
-
-## Examples
-
-??? example
-
-    The example below is the same as [`json_editable_document`'s](json_editable_document.md): every view read back
-    out of the document -- `#!cpp doc.root()` and the views nested under it -- sees the edits made through `set`.
-
-    ```cpp
-    --8<-- "examples/json_editable_document.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/json_editable_document.output"
-    ```
-
-## See also
-
-- [json_editable_document](json_editable_document.md) - the document type this view refers into
-- [json_view](json_view.md) - the corresponding read-only view
-- [ordered_json_editable_view](ordered_json_editable_view.md) - the corresponding view for
-  `ordered_json_editable_document`
-
-## Version history
-
-Since version 3.13.0.

docs/mkdocs/docs/api/json_sax/binary_t.md

@@ -1,30 +0,0 @@
-# <small>nlohmann::json_sax::</small>binary_t
-
-```cpp
-using binary_t = typename BasicJsonType::binary_t;
-```
-
-The type used by the [`binary`](binary.md) callback for JSON binary values, forwarded from the
-`BasicJsonType` template parameter.
-
-See [`basic_json::binary_t`](../basic_json/binary_t.md) for more information.
-
-## Examples
-
-??? example
-
-    The example shows the type `binary_t` and its relation to `basic_json::binary_t`.
-
-    ```cpp
-    --8<-- "examples/json_sax__binary_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/json_sax__binary_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.8.0.

docs/mkdocs/docs/api/json_sax/json_sax.md

@@ -1,33 +0,0 @@
-# <small>nlohmann::json_sax::</small>json_sax
-
-```cpp
-// (1)
-json_sax() = default;
-
-// (2)
-json_sax(const json_sax&) = default;
-
-// (3)
-json_sax(json_sax&&) noexcept = default;
-```
-
-1. Default constructor.
-2. Copy constructor.
-3. Move constructor.
-
-`json_sax` is a pure abstract base class with no data members of its own, so all three constructors are
-defaulted and only exist to make derived SAX consumers explicitly copyable/movable.
-
-## Exception safety
-
-No-throw guarantee: none of these constructors throw exceptions.
-
-## Complexity
-
-Constant.
-
-<!-- NOLINT Examples -->
-
-## Version history
-
-- Added in version 3.2.0.

docs/mkdocs/docs/api/json_sax/number_float_t.md

@@ -1,30 +0,0 @@
-# <small>nlohmann::json_sax::</small>number_float_t
-
-```cpp
-using number_float_t = typename BasicJsonType::number_float_t;
-```
-
-The type used by the [`number_float`](number_float.md) callback for JSON floating-point numbers,
-forwarded from the `BasicJsonType` template parameter.
-
-See [`basic_json::number_float_t`](../basic_json/number_float_t.md) for more information.
-
-## Examples
-
-??? example
-
-    The example shows the type `number_float_t` and its relation to `basic_json::number_float_t`.
-
-    ```cpp
-    --8<-- "examples/json_sax__number_float_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/json_sax__number_float_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.2.0.

docs/mkdocs/docs/api/json_sax/number_integer_t.md

@@ -1,30 +0,0 @@
-# <small>nlohmann::json_sax::</small>number_integer_t
-
-```cpp
-using number_integer_t = typename BasicJsonType::number_integer_t;
-```
-
-The type used by the [`number_integer`](number_integer.md) callback for JSON integer numbers, forwarded
-from the `BasicJsonType` template parameter.
-
-See [`basic_json::number_integer_t`](../basic_json/number_integer_t.md) for more information.
-
-## Examples
-
-??? example
-
-    The example shows the type `number_integer_t` and its relation to `basic_json::number_integer_t`.
-
-    ```cpp
-    --8<-- "examples/json_sax__number_integer_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/json_sax__number_integer_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.2.0.

docs/mkdocs/docs/api/json_sax/number_unsigned_t.md

@@ -1,30 +0,0 @@
-# <small>nlohmann::json_sax::</small>number_unsigned_t
-
-```cpp
-using number_unsigned_t = typename BasicJsonType::number_unsigned_t;
-```
-
-The type used by the [`number_unsigned`](number_unsigned.md) callback for JSON unsigned integer numbers,
-forwarded from the `BasicJsonType` template parameter.
-
-See [`basic_json::number_unsigned_t`](../basic_json/number_unsigned_t.md) for more information.
-
-## Examples
-
-??? example
-
-    The example shows the type `number_unsigned_t` and its relation to `basic_json::number_unsigned_t`.
-
-    ```cpp
-    --8<-- "examples/json_sax__number_unsigned_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/json_sax__number_unsigned_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.2.0.

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

@@ -1,29 +0,0 @@
-# <small>nlohmann::json_sax::</small>operator=
-
-```cpp
-// (1)
-json_sax& operator=(const json_sax&) = default;
-
-// (2)
-json_sax& operator=(json_sax&&) noexcept = default;
-```
-
-1. Copy assignment operator.
-2. Move assignment operator.
-
-`json_sax` is a pure abstract base class with no data members of its own, so both assignment operators
-are defaulted and only exist to make derived SAX consumers explicitly copy-/move-assignable.
-
-## Exception safety
-
-No-throw guarantee: neither operator throws exceptions.
-
-## Complexity
-
-Constant.
-
-<!-- NOLINT Examples -->
-
-## Version history
-
-- Added in version 3.2.0.

docs/mkdocs/docs/api/json_sax/string_t.md

@@ -1,30 +0,0 @@
-# <small>nlohmann::json_sax::</small>string_t
-
-```cpp
-using string_t = typename BasicJsonType::string_t;
-```
-
-The type used by the [`string`](string.md) and [`key`](key.md) callbacks for JSON strings and object
-keys, forwarded from the `BasicJsonType` template parameter.
-
-See [`basic_json::string_t`](../basic_json/string_t.md) for more information.
-
-## Examples
-
-??? example
-
-    The example shows the type `string_t` and its relation to `basic_json::string_t`.
-
-    ```cpp
-    --8<-- "examples/json_sax__string_t.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/json_sax__string_t.output"
-    ```
-
-## Version history
-
-- Added in version 3.2.0.

docs/mkdocs/docs/api/json_sax/~json_sax.md

@@ -1,22 +0,0 @@
-# <small>nlohmann::json_sax::</small>~json_sax
-
-```cpp
-virtual ~json_sax() = default;
-```
-
-Destructor. Virtual to allow proper destruction of derived SAX consumer classes through a
-pointer/reference to `json_sax`.
-
-## Exception safety
-
-No-throw guarantee: this destructor never throws exceptions.
-
-## Complexity
-
-Constant.
-
-<!-- NOLINT Examples -->
-
-## Version history
-
-- Added in version 3.2.0.

docs/mkdocs/docs/api/macros/index.md

@@ -42,8 +42,6 @@ header. See also the [macro overview page](../../features/macros.md).
 - [**JSON_SKIP_UNSUPPORTED_COMPILER_CHECK**](json_skip_unsupported_compiler_check.md) - do not warn about unsupported compilers
 - [**JSON_USE_GLOBAL_UDLS**](json_use_global_udls.md) - place user-defined string literals (UDLs) into the global namespace
 - [**JSON_USE_SIMDUTF**](json_use_simdutf.md) - use the simdutf library to accelerate UTF-8 validation
-- [**JSON_VIEW_NO_SIMD**](json_view_no_simd.md) - use only portable code in the parser of `json_view.hpp`
-- [**JSON_VIEW_USE_SSSE3**](json_view_use_ssse3.md) - validate non-ASCII strings with SSSE3 in the parser of `json_view.hpp`
 
 ## Library version
 

docs/mkdocs/docs/api/macros/json_disable_unlocked_file_io.md

@@ -10,9 +10,6 @@ earlier, instead of locking the file once and reading it with the unlocked stdio
 It does not change any result: values, exceptions, and the position of the file after parsing are the same either way.
 Only the speed and the locking of the file differ (see the notes on locking below).
 
-Builds with MemorySanitizer use `std::fgetc` automatically, because the inline `getc_unlocked` of glibc reads the stdio
-buffer directly, which glibc (not instrumented) filled, and MemorySanitizer would report it as uninitialized.
-
 ## Default definition
 
 The default value is `0`: the file is locked once and read with the unlocked stdio functions where they are available.

docs/mkdocs/docs/api/macros/json_view_no_simd.md

@@ -1,52 +0,0 @@
-# JSON_VIEW_NO_SIMD
-
-```cpp
-#define JSON_VIEW_NO_SIMD
-```
-
-When defined, the parser of [`basic_json_document`](../basic_json_document/index.md) (`<nlohmann/json_view.hpp>`)
-uses only portable C++ to scan strings. By default, it scans long runs of string bytes 16 at a time with NEON on
-AArch64 (with GCC and Clang) and SSE2 on x86-64, which are part of the baseline instruction sets of these
-architectures, and validates non-ASCII text with NEON (or SSSE3, see
-[`JSON_VIEW_USE_SSSE3`](json_view_use_ssse3.md)).
-
-The same input is accepted or rejected either way, with the same values, and errors are reported the same way; only
-the speed differs. The macro exists for platforms whose compilers lack the intrinsics headers, and to test the portable
-code.
-
-!!! note "ABI compatibility"
-
-    The macro selects between two definitions of the same inline functions. Whether it is defined is encoded in the
-    [namespace](../../features/namespace.md) (tag `_vns`), resulting in distinct symbol names. Translation units
-    compiled with and without it can therefore be linked into the same program without One Definition Rule (ODR)
-    violations, but they cannot exchange instances of library types.
-
-## Default definition
-
-By default, `#!cpp JSON_VIEW_NO_SIMD` is not defined, and the vector code is used where available.
-
-```cpp
-#undef JSON_VIEW_NO_SIMD
-```
-
-## Examples
-
-??? example
-
-    The code below uses the portable string scanning of the view.
-
-    ```cpp
-    #define JSON_VIEW_NO_SIMD
-    #include <nlohmann/json_view.hpp>
-
-    ...
-    ```
-
-## See also
-
-- [JSON_VIEW_USE_SSSE3](json_view_use_ssse3.md) - validate non-ASCII strings with SSSE3 on x86-64
-- [json_view](../../features/json_view.md) - the zero-copy view
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/macros/json_view_use_ssse3.md

@@ -1,53 +0,0 @@
-# JSON_VIEW_USE_SSSE3
-
-```cpp
-#define JSON_VIEW_USE_SSSE3
-```
-
-When defined on x86-64, the parser of [`basic_json_document`](../basic_json_document/index.md)
-(`<nlohmann/json_view.hpp>`) validates non-ASCII text in strings with SSSE3 without asking the CPU first.
-
-By default, the parser checks once at run time whether the CPU has SSSE3 (all x86-64 CPUs since about 2011 have it)
-and then validates non-ASCII text 16 bytes at a time, using the "lookup4" algorithm of
-[simdjson](https://github.com/simdjson/simdjson); on CPUs without SSSE3, it validates one UTF-8 sequence at a time.
-The vector check is compiled for SSSE3 with a function attribute (GCC 4.9 and later, Clang), so this needs no compiler
-option. With MSVC, the check uses `__cpuid`. On AArch64, the vector check uses NEON and is always on.
-
-Define the macro only together with a compiler option that enables SSSE3 (e.g. `-mssse3`, or `-march=` with a CPU that
-has it), and only for programs that run on such CPUs. It saves the check of the CPU, which costs little. The same
-input is accepted or rejected either way; only the speed of non-ASCII text differs.
-
-!!! note "ABI compatibility"
-
-    The macro selects between two definitions of the same inline functions. Whether it is defined is encoded in the
-    [namespace](../../features/namespace.md) (tag `_vssse3`, on every architecture), resulting in distinct symbol
-    names. Translation units compiled with and without it can therefore be linked into the same program without One
-    Definition Rule (ODR) violations, but they cannot exchange instances of library types.
-
-## Default definition
-
-By default, `#!cpp JSON_VIEW_USE_SSSE3` is not defined.
-
-```cpp
-#undef JSON_VIEW_USE_SSSE3
-```
-
-## Examples
-
-??? example
-
-    With CMake, for a program that only runs on CPUs with SSSE3:
-
-    ```cmake
-    target_compile_definitions(your_target PRIVATE JSON_VIEW_USE_SSSE3)
-    target_compile_options(your_target PRIVATE -mssse3)
-    ```
-
-## See also
-
-- [JSON_VIEW_NO_SIMD](json_view_no_simd.md) - use only portable code in the view's parser
-- [JSON_USE_SIMDUTF](json_use_simdutf.md) - validate UTF-8 with simdutf in `basic_json`'s parser
-
-## Version history
-
-- Added in version 3.13.0.

docs/mkdocs/docs/api/macros/nlohmann_json_namespace.md

@@ -39,6 +39,6 @@ the library.
 ## Version history
 
 - Added in version 3.11.0. Changed inline namespace name in version 3.11.2. Added the ABI tag `_dp` in
-  version 3.12.0, and the ABI tags `_bics`, `_psp`, `_snul`, `_sbu8`, `_ekmo`, `_dsbs`, `_dufio`, `_vns`, and
-  `_vssse3` in version 3.13.0; see
+  version 3.12.0, and the ABI tags `_bics`, `_psp`, `_snul`, `_sbu8`, `_ekmo`, `_dsbs`, and `_dufio` in version
+  3.13.0; see
   [`nlohmann` Namespace](../../features/namespace.md#structure).

docs/mkdocs/docs/api/ordered_json.md

@@ -8,16 +8,16 @@ This type preserves the insertion order of object keys.
 
 ## Iterator invalidation
 
-The type is based on [`ordered_map`](ordered_map/index.md) which in turn uses a `std::vector` to store object elements.
+The type is based on [`ordered_map`](ordered_map.md) which in turn uses a `std::vector` to store object elements.
 Therefore, adding object elements can yield a reallocation in which case all iterators (including the
 [`end()`](basic_json/end.md) iterator) and all references to the elements are invalidated. Also, any iterator or
 reference after the insertion point will point to the same index, which is now a different value.
 
 ## Complexity
 
-[`ordered_map`](ordered_map/index.md) has no lookup index: every key-based object operation is a linear scan, so building or
+[`ordered_map`](ordered_map.md) has no lookup index: every key-based object operation is a linear scan, so building or
 parsing an object of `n` keys costs O(n²) rather than O(n log n). See
-[`ordered_map` complexity](ordered_map/index.md#complexity) for the per-operation table and for measured numbers.
+[`ordered_map` complexity](ordered_map.md#complexity) for the per-operation table and for measured numbers.
 
 ## Examples
 
@@ -37,7 +37,7 @@ parsing an object of `n` keys costs O(n²) rather than O(n log n). See
 
 ## See also
 
-- [ordered_map](ordered_map/index.md)
+- [ordered_map](ordered_map.md)
 - [Object Order](../features/object_order.md)
 
 ## Version history

docs/mkdocs/docs/api/ordered_json_editable_document.md

@@ -1,47 +0,0 @@
-# <small>nlohmann::</small>ordered_json_editable_document
-
-<small>Defined in header `<nlohmann/json_view.hpp>`</small>
-
-```cpp
-using ordered_json_editable_document = basic_json_document<ordered_json, true>;
-```
-
-This type is an **editable** [`basic_json_document`](basic_json_document/index.md) of the
-[`ordered_json`](ordered_json.md) specialization: [`set`](basic_json_document/set.md) and
-[`push_back`](basic_json_document/push_back.md) change values after parsing, as for
-[`json_editable_document`](json_editable_document.md), and
-[`materialize()`](basic_json_view/materialize.md) preserves the document order of object members -- including
-members [`set`](basic_json_document/set.md) added -- instead of sorting them like
-[`json_editable_document`](json_editable_document.md) does.
-
-## Examples
-
-??? example
-
-    The example below edits a document with `set`, then shows that `materialize()` keeps the member order of the
-    source text (with the new member at the end) for `ordered_json_editable_document`, where it would sort the
-    members alphabetically for [`json_editable_document`](json_editable_document.md).
-
-    ```cpp
-    --8<-- "examples/ordered_json_editable_document.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/ordered_json_editable_document.output"
-    ```
-
-## See also
-
-- [ordered_json_editable_view](ordered_json_editable_view.md) - a view of a value of an
-  `ordered_json_editable_document`
-- [ordered_json_document](ordered_json_document.md) - the read-only document this type adds edits to
-- [json_editable_document](json_editable_document.md) - the corresponding editable document for the default `json`
-  specialization
-- [Object Order](../features/object_order.md)
-- [Edits](basic_json_document/index.md#edits) - what an edit guarantees
-
-## Version history
-
-Since version 3.13.0.

docs/mkdocs/docs/api/ordered_json_editable_view.md

@@ -1,40 +0,0 @@
-# <small>nlohmann::</small>ordered_json_editable_view
-
-<small>Defined in header `<nlohmann/json_view.hpp>`</small>
-
-```cpp
-using ordered_json_editable_view = basic_json_view<ordered_json, true>;
-```
-
-This type is a [`basic_json_view`](basic_json_view/index.md) of a value of an
-[`ordered_json_editable_document`](ordered_json_editable_document.md), the corresponding view for
-[`ordered_json_view`](ordered_json_view.md) the way [`json_editable_view`](json_editable_view.md) is for
-[`json_view`](json_view.md).
-
-## Examples
-
-??? example
-
-    The example below is the same as [`ordered_json_editable_document`'s](ordered_json_editable_document.md): the
-    views `set` returns see the document's member order preserved on `materialize()`, unlike for a
-    [`json_editable_document`](json_editable_document.md).
-
-    ```cpp
-    --8<-- "examples/ordered_json_editable_document.cpp"
-    ```
-
-    Output:
-
-    ```json
-    --8<-- "examples/ordered_json_editable_document.output"
-    ```
-
-## See also
-
-- [ordered_json_editable_document](ordered_json_editable_document.md) - the document type this view refers into
-- [ordered_json_view](ordered_json_view.md) - the corresponding read-only view
-- [json_editable_view](json_editable_view.md) - the corresponding view for `json_editable_document`
-
-## Version history
-
-Since version 3.13.0.

docs/mkdocs/docs/api/ordered_map.md

@@ -6,7 +6,7 @@ template<class Key, class T, class IgnoredLess = std::less<Key>,
 struct ordered_map : std::vector<std::pair<const Key, T>, Allocator>;
 ```
 
-A minimal map-like container that preserves insertion order for use within [`nlohmann::ordered_json`](../ordered_json.md)
+A minimal map-like container that preserves insertion order for use within [`nlohmann::ordered_json`](ordered_json.md)
 (`nlohmann::basic_json<ordered_map>`).
 
 ## Template parameters
@@ -30,19 +30,19 @@ case all iterators (including the `end()` iterator) and all references to the el
 
 When the storage grows, the keys are copied and the mapped values are moved to the new storage. A plain `std::vector`
 would copy the whole elements instead, because their `#!cpp const` keys make them not nothrow move constructible; for
-[`ordered_json`](../ordered_json.md), this would be a deep copy of every nested value. The values are only copied if
+[`ordered_json`](ordered_json.md), this would be a deep copy of every nested value. The values are only copied if
 `T` is not default constructible or not nothrow move assignable.
 
 ## Member types
 
 - **key_type** - key type (`Key`)
 - **mapped_type** - mapped type (`T`)
-- [**Container**](Container.md) - base container type (`#!cpp std::vector<std::pair<const Key, T>, Allocator>`)
+- **Container** - base container type (`#!cpp std::vector<std::pair<const Key, T>, Allocator>`)
 - **iterator**
 - **const_iterator**
 - **size_type**
 - **value_type**
-- [**key_compare**](key_compare.md) - key comparison function
+- **key_compare** - key comparison function
 ```cpp
 std::equal_to<Key>  // until C++14
 
@@ -51,16 +51,15 @@ std::equal_to<>     // since C++14
 
 ## Member functions
 
-- [(constructor)](ordered_map.md)
-- [(destructor)](~ordered_map.md)
-- [**operator=**](operator=.md)
-- [**emplace**](emplace.md)
-- [**operator\[\]**](operator[].md)
-- [**at**](at.md)
-- [**erase**](erase.md)
-- [**count**](count.md)
-- [**find**](find.md)
-- [**insert**](insert.md)
+- (constructor)
+- (destructor)
+- **emplace**
+- **operator\[\]**
+- **at**
+- **erase**
+- **count**
+- **find**
+- **insert**
 
 ## Exception safety
 
@@ -90,7 +89,7 @@ This differs from `#!cpp std::map`, where the same operations are O(log n).
 !!! warning "Quadratic cost of building large objects"
 
     Because every insertion scans all elements inserted so far, building an object of `n` distinct keys costs
-    **O(n²)** in total. This applies to filling an [`ordered_json`](../ordered_json.md) object key by key as well as to
+    **O(n²)** in total. This applies to filling an [`ordered_json`](ordered_json.md) object key by key as well as to
     parsing one, since the parser inserts each key as it is read.
 
     The cost is negligible for the object sizes typically found in configuration files or API payloads, but it grows
@@ -107,7 +106,7 @@ This differs from `#!cpp std::map`, where the same operations are O(log n).
     If key order matters for objects of that size, consider a container with a lookup index, such as
     [`nlohmann::fifo_map`](https://github.com/nlohmann/fifo_map)
     ([integration](https://github.com/nlohmann/json/issues/485#issuecomment-333652309)), as the object type -- see
-    [object order](../../features/object_order.md).
+    [object order](../features/object_order.md).
 
 ## Examples
 
@@ -127,10 +126,10 @@ This differs from `#!cpp std::map`, where the same operations are O(log n).
 
 ## See also
 
-- [ordered_json](../ordered_json.md)
+- [ordered_json](ordered_json.md)
 
 ## Version history
 
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).
+- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](ordered_json.md).
 - Added **key_compare** member in version 3.11.0.
 - Changed in version 3.13.0: growing the storage moves the mapped values instead of copying them.

docs/mkdocs/docs/api/ordered_map/Container.md

@@ -1,28 +0,0 @@
-# <small>nlohmann::ordered_map::</small>Container
-
-```cpp
-using Container = std::vector<std::pair<const Key, T>, Allocator>;
-```
-
-The base container type that `ordered_map` publicly inherits from. Elements are stored in insertion
-order as `#!cpp std::pair<const Key, T>` entries in a `std::vector`.
-
-## Examples
-
-??? example
-
-    The example shows the type `Container`.
-
-    ```cpp
-    --8<-- "examples/ordered_map__Container.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__Container.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).

docs/mkdocs/docs/api/ordered_map/at.md

@@ -1,61 +0,0 @@
-# <small>nlohmann::ordered_map::</small>at
-
-```cpp
-// (1)
-T& at(const key_type& key);
-const T& at(const key_type& key) const;
-
-// (2)
-template<class KeyType>
-T& at(KeyType&& key);
-template<class KeyType>
-const T& at(KeyType&& key) const;
-```
-
-1. Returns a reference to the value mapped to `key`.
-2. Same as (1), but for any `KeyType` comparable to `key_type` via [`key_compare`](key_compare.md)
-   (heterogeneous lookup, e.g. looking up by a `#!cpp const char*` without constructing a temporary
-   `key_type`). Only participates in overload resolution if `KeyType` is usable as a key type.
-
-## Template parameters
-
-`KeyType`
-:   a type comparable to `key_type` via [`key_compare`](key_compare.md)
-
-## Parameters
-
-`key` (in)
-:   key of the element to find
-
-## Return value
-
-reference to the mapped value of the element with key equal to `key`
-
-## Exceptions
-
-Throws `std::out_of_range` if no element with key `key` exists.
-
-## Complexity
-
-Linear in the number of elements.
-
-## Examples
-
-??? example
-
-    The example shows how `at` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__at.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__at.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.1 to implement [`nlohmann::ordered_json`](../ordered_json.md).
-- Overload (2) added in version 3.11.0.

docs/mkdocs/docs/api/ordered_map/count.md

@@ -1,53 +0,0 @@
-# <small>nlohmann::ordered_map::</small>count
-
-```cpp
-// (1)
-size_type count(const key_type& key) const;
-
-// (2)
-template<class KeyType>
-size_type count(KeyType&& key) const;
-```
-
-1. Returns the number of elements with key equal to `key` (0 or 1, since keys are unique).
-2. Same as (1), but for any `KeyType` comparable to `key_type` via [`key_compare`](key_compare.md)
-   (heterogeneous lookup). Only participates in overload resolution if `KeyType` is usable as a key type.
-
-## Template parameters
-
-`KeyType`
-:   a type comparable to `key_type` via [`key_compare`](key_compare.md)
-
-## Parameters
-
-`key` (in)
-:   key of the elements to count
-
-## Return value
-
-number of elements with key equal to `key` (0 or 1)
-
-## Complexity
-
-Linear in the number of elements.
-
-## Examples
-
-??? example
-
-    The example shows how `count` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__count.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__count.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.1 to implement [`nlohmann::ordered_json`](../ordered_json.md).
-- Overload (2) added in version 3.11.0.

docs/mkdocs/docs/api/ordered_map/emplace.md

@@ -1,58 +0,0 @@
-# <small>nlohmann::ordered_map::</small>emplace
-
-```cpp
-// (1)
-std::pair<iterator, bool> emplace(const key_type& key, T&& t);
-
-// (2)
-template<class KeyType>
-std::pair<iterator, bool> emplace(KeyType&& key, T&& t);
-```
-
-1. Inserts `#!cpp {key, t}` if no element with an equal key already exists (per [`key_compare`](key_compare.md)),
-   appending it at the end to preserve insertion order. If an equal key already exists, does nothing.
-2. Same as (1), but for any `KeyType` comparable to `key_type` via [`key_compare`](key_compare.md)
-   (heterogeneous lookup). Only participates in overload resolution if `KeyType` is usable as a key type.
-
-## Template parameters
-
-`KeyType`
-:   a type comparable to `key_type` via [`key_compare`](key_compare.md)
-
-## Parameters
-
-`key` (in)
-:   key of the element to insert
-
-`t` (in)
-:   value of the element to insert
-
-## Return value
-
-pair of an iterator to the (possibly newly inserted) element, and a `bool` that is `true` if insertion
-took place and `false` if an element with an equal key already existed
-
-## Complexity
-
-Linear in the number of elements.
-
-## Examples
-
-??? example
-
-    The example shows how `emplace` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__emplace.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__emplace.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).
-- Overload (2) added in version 3.11.0.

docs/mkdocs/docs/api/ordered_map/erase.md

@@ -1,75 +0,0 @@
-# <small>nlohmann::ordered_map::</small>erase
-
-```cpp
-// (1)
-size_type erase(const key_type& key);
-
-// (2)
-template<class KeyType>
-size_type erase(KeyType&& key);
-
-// (3)
-iterator erase(iterator pos);
-
-// (4)
-iterator erase(iterator first, iterator last);
-```
-
-1. Removes the element with key equal to `key`, if any, preserving the relative order of the remaining
-   elements.
-2. Same as (1), but for any `KeyType` comparable to `key_type` via [`key_compare`](key_compare.md)
-   (heterogeneous lookup). Only participates in overload resolution if `KeyType` is usable as a key type.
-3. Removes the element at `pos`.
-4. Removes the elements in range `[first, last)`.
-
-## Template parameters
-
-`KeyType`
-:   a type comparable to `key_type` via [`key_compare`](key_compare.md)
-
-## Parameters
-
-`key` (in)
-:   key of the element to remove
-
-`pos` (in)
-:   iterator to the element to remove
-
-`first` (in)
-:   iterator to the first element to remove
-
-`last` (in)
-:   iterator one past the last element to remove
-
-## Return value
-
-1. number of elements removed (0 or 1)
-2. number of elements removed (0 or 1)
-3. iterator following the removed element
-4. iterator following the last removed element
-
-## Complexity
-
-Linear in the number of elements (elements after the removed one(s) are shifted to keep storage
-contiguous).
-
-## Examples
-
-??? example
-
-    The example shows how `erase` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__erase.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__erase.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).
-- Overload (2) added in version 3.11.0.

docs/mkdocs/docs/api/ordered_map/find.md

@@ -1,56 +0,0 @@
-# <small>nlohmann::ordered_map::</small>find
-
-```cpp
-// (1)
-iterator find(const key_type& key);
-const_iterator find(const key_type& key) const;
-
-// (2)
-template<class KeyType>
-iterator find(KeyType&& key);
-template<class KeyType>
-const_iterator find(KeyType&& key) const;
-```
-
-1. Returns an iterator to the element with key equal to `key`, or `end()` if no such element exists.
-2. Same as (1), but for any `KeyType` comparable to `key_type` via [`key_compare`](key_compare.md)
-   (heterogeneous lookup). Only participates in overload resolution if `KeyType` is usable as a key type.
-
-## Template parameters
-
-`KeyType`
-:   a type comparable to `key_type` via [`key_compare`](key_compare.md)
-
-## Parameters
-
-`key` (in)
-:   key of the element to find
-
-## Return value
-
-iterator to the element with key equal to `key`, or `end()` if not found
-
-## Complexity
-
-Linear in the number of elements.
-
-## Examples
-
-??? example
-
-    The example shows how `find` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__find.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__find.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.1 to implement [`nlohmann::ordered_json`](../ordered_json.md).
-- Overload (2) added in version 3.11.0.

docs/mkdocs/docs/api/ordered_map/insert.md

@@ -1,63 +0,0 @@
-# <small>nlohmann::ordered_map::</small>insert
-
-```cpp
-// (1)
-std::pair<iterator, bool> insert(value_type&& value);
-std::pair<iterator, bool> insert(const value_type& value);
-
-// (2)
-template<typename InputIt>
-void insert(InputIt first, InputIt last);
-```
-
-1. Inserts `value` if no element with an equal key already exists (per [`key_compare`](key_compare.md)),
-   appending it at the end to preserve insertion order. If an equal key already exists, does nothing.
-2. Inserts the elements from range `[first, last)`, in iteration order, applying the same equal-key rule
-   as (1) to each element.
-
-## Template parameters
-
-`InputIt`
-:   an input iterator type
-
-## Parameters
-
-`value` (in)
-:   value to insert
-
-`first` (in)
-:   iterator to the first element to insert
-
-`last` (in)
-:   iterator one past the last element to insert
-
-## Return value
-
-1. pair of an iterator to the (possibly newly inserted) element, and a `bool` that is `true` if insertion
-   took place and `false` if an element with an equal key already existed
-2. (none)
-
-## Complexity
-
-1. Linear in the number of elements.
-2. Linear in the distance between `first` and `last`, times linear in the number of elements.
-
-## Examples
-
-??? example
-
-    The example shows how `insert` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__insert.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__insert.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.1 to implement [`nlohmann::ordered_json`](../ordered_json.md).

docs/mkdocs/docs/api/ordered_map/key_compare.md

@@ -1,34 +0,0 @@
-# <small>nlohmann::ordered_map::</small>key_compare
-
-```cpp
-using key_compare = std::equal_to<Key>;  // until C++14
-
-using key_compare = std::equal_to<>;     // since C++14
-```
-
-The comparator used to determine key equality when looking up elements. Unlike `std::map`, `ordered_map`
-uses linear search with `key_compare` rather than an ordering relation, since element order reflects
-insertion order rather than key order.
-
-Since C++14, the transparent `#!cpp std::equal_to<>` is used, which enables heterogeneous lookup (e.g.
-looking up by a `#!cpp const char*` key without constructing a temporary `Key`).
-
-## Examples
-
-??? example
-
-    The example shows how `key_compare` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__key_compare.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__key_compare.output"
-    ```
-
-## Version history
-
-- Added in version 3.11.0.

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

@@ -1,32 +0,0 @@
-# <small>nlohmann::ordered_map::</small>operator=
-
-```cpp
-// (1)
-ordered_map& operator=(const ordered_map& other);
-
-// (2)
-ordered_map& operator=(ordered_map&& other) noexcept(std::is_nothrow_move_assignable<Container>::value);
-```
-
-1. Copy assignment operator.
-2. Move assignment operator.
-
-## Parameters
-
-`other` (in)
-:   value to assign from
-
-## Return value
-
-`*this`
-
-## Complexity
-
-1. Linear in the size of `other`.
-2. Constant.
-
-<!-- NOLINT Examples -->
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).

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

@@ -1,62 +0,0 @@
-# <small>nlohmann::ordered_map::</small>operator[]
-
-```cpp
-// (1)
-T& operator[](const key_type& key);
-const T& operator[](const key_type& key) const;
-
-// (2)
-template<class KeyType>
-T& operator[](KeyType&& key);
-template<class KeyType>
-const T& operator[](KeyType&& key) const;
-```
-
-1. Returns a reference to the value mapped to `key`, inserting a default-constructed `T` (non-`const`
-   overload only) if no such element exists yet.
-2. Same as (1), but for any `KeyType` comparable to `key_type` via [`key_compare`](key_compare.md)
-   (heterogeneous lookup). Only participates in overload resolution if `KeyType` is usable as a key type.
-
-## Template parameters
-
-`KeyType`
-:   a type comparable to `key_type` via [`key_compare`](key_compare.md)
-
-## Parameters
-
-`key` (in)
-:   key of the element to find or insert
-
-## Return value
-
-reference to the mapped value of the element with key equal to `key`
-
-## Exceptions
-
-The `const` overloads throw `std::out_of_range` if no element with key `key` exists (they delegate to
-[`at`](at.md)).
-
-## Complexity
-
-Linear in the number of elements.
-
-## Examples
-
-??? example
-
-    The example shows how `operator[]` is used.
-
-    ```cpp
-    --8<-- "examples/ordered_map__operator_idx.cpp"
-    ```
-
-    Output:
-
-    ```
-    --8<-- "examples/ordered_map__operator_idx.output"
-    ```
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).
-- Overload (2) added in version 3.11.0.

docs/mkdocs/docs/api/ordered_map/ordered_map.md

@@ -1,66 +0,0 @@
-# <small>nlohmann::ordered_map::</small>ordered_map
-
-```cpp
-// (1)
-ordered_map() noexcept(noexcept(Container()));
-
-// (2)
-explicit ordered_map(const Allocator& alloc) noexcept(noexcept(Container(alloc)));
-
-// (3)
-template <class It>
-ordered_map(It first, It last, const Allocator& alloc = Allocator());
-
-// (4)
-ordered_map(std::initializer_list<value_type> init, const Allocator& alloc = Allocator());
-
-// (5)
-ordered_map(const ordered_map&) = default;
-
-// (6)
-ordered_map(ordered_map&&) noexcept(std::is_nothrow_move_constructible<Container>::value) = default;
-```
-
-1. Default constructor. Creates an empty `ordered_map`.
-2. Creates an empty `ordered_map` using the given allocator.
-3. Creates an `ordered_map` from the elements in range `[first, last)`, inserted in iteration order.
-4. Creates an `ordered_map` from an initializer list of key/value pairs, inserted in list order.
-5. Copy constructor.
-6. Move constructor.
-
-These constructors are declared explicitly (rather than inherited via `#!cpp using Container::Container`)
-because older compilers (GCC <= 5.5, Xcode <= 9.4) do not handle the inherited constructors correctly.
-
-## Template parameters
-
-`It`
-:   an input iterator type
-
-## Parameters
-
-`alloc` (in)
-:   allocator to use for the underlying container
-
-`first` (in)
-:   iterator to the first element to insert
-
-`last` (in)
-:   iterator one past the last element to insert
-
-`init` (in)
-:   initializer list of key/value pairs to insert
-
-## Complexity
-
-1. Constant.
-2. Constant.
-3. Linear in the distance between `first` and `last`.
-4. Linear in the size of `init`.
-5. Linear in the size of `other`.
-6. Constant.
-
-<!-- NOLINT Examples -->
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).

docs/mkdocs/docs/api/ordered_map/~ordered_map.md

@@ -1,17 +0,0 @@
-# <small>nlohmann::ordered_map::</small>~ordered_map
-
-```cpp
-~ordered_map() = default;
-```
-
-Destroys the `ordered_map` and frees all allocated memory.
-
-## Complexity
-
-Linear in the number of elements.
-
-<!-- NOLINT Examples -->
-
-## Version history
-
-- Added in version 3.9.0 to implement [`nlohmann::ordered_json`](../ordered_json.md).

docs/mkdocs/docs/examples/basic_json_document__erase.cpp

@@ -1,38 +0,0 @@
-#include <iostream>
-#include <nlohmann/json_view.hpp>
-
-using json = nlohmann::json;
-using json_editable_document = nlohmann::json_editable_document;
-using json_editable_view = nlohmann::json_editable_view;
-
-int main()
-{
-    // a deprecated field is dropped from a configuration file, and a
-    // decommissioned replica is removed from the list -- "price" keeps its
-    // trailing zero, and the fields around the removed ones keep their order
-    const std::string text = R"({
-  "name": "cache",
-  "legacy_host": "db0",
-  "host": "db1",
-  "price": 19.90,
-  "replicas": ["db2", "db3", "db4"]
-})";
-
-    json_editable_document doc = json_editable_document::parse(text);
-
-    doc.erase(doc.root(), "legacy_host");                                      // (1) an object member
-    doc.erase(doc.root()["replicas"], 1);                                      // (2) an array element ("db3")
-    const std::size_t removed = doc.erase(json::json_pointer("/replicas/0"));  // (3) via a JSON pointer
-
-    std::cout << removed << '\n';
-    std::cout << doc.root().dump(2, ' ', false, json_editable_view::number_format::source) << "\n\n";
-
-    // the same edits on a plain json value: object_t is a std::map, so
-    // parsing already sorted the keys, and dump() rewrites every number to
-    // its shortest form, even "price", which was never touched
-    json plain = json::parse(text);
-    plain.erase("legacy_host");
-    plain["replicas"].erase(1);
-    plain["replicas"].erase(0);
-    std::cout << plain.dump(2) << '\n';
-}

docs/mkdocs/docs/examples/basic_json_document__erase.output

@@ -1,18 +0,0 @@
-1
-{
-  "name": "cache",
-  "host": "db1",
-  "price": 19.90,
-  "replicas": [
-    "db4"
-  ]
-}
-
-{
-  "host": "db1",
-  "name": "cache",
-  "price": 19.9,
-  "replicas": [
-    "db4"
-  ]
-}

docs/mkdocs/docs/examples/basic_json_document__insert.cpp

@@ -1,38 +0,0 @@
-#include <iostream>
-#include <nlohmann/json_view.hpp>
-
-using json = nlohmann::json;
-using json_editable_document = nlohmann::json_editable_document;
-using json_editable_view = nlohmann::json_editable_view;
-
-int main()
-{
-    // a deployment plan -- "budget" is written with a trailing zero that has
-    // no effect on its value
-    const std::string text = R"({
-  "release": "2026.09",
-  "steps": ["build", "test", "deploy"],
-  "budget": 19.90
-})";
-
-    json_editable_document doc = json_editable_document::parse(text);
-
-    const std::size_t deploy_index = 2;
-    const auto deploy = doc.root()["steps"][deploy_index];  // held across the insert
-
-    doc.insert(doc.root()["steps"], deploy_index, "smoke-test"); // insert before "deploy"
-
-    // the held view still refers to "deploy", even though its index moved
-    // from 2 to 3, and nothing else in the document was touched
-    std::cout << deploy.dump() << '\n';
-    std::cout << doc.root().dump(2, ' ', false, json_editable_view::number_format::source) << "\n\n";
-
-    // the same edit on a plain json value: an index held from before the
-    // insert now refers to whatever moved into that slot, and dump()
-    // rewrites "budget" to its shortest form even though it was never
-    // touched
-    json plain = json::parse(text);
-    plain["steps"].insert(plain["steps"].begin() + static_cast<std::ptrdiff_t>(deploy_index), "smoke-test");
-    std::cout << plain["steps"][deploy_index].dump() << '\n';
-    std::cout << plain.dump(2) << '\n';
-}

docs/mkdocs/docs/examples/basic_json_document__insert.output

@@ -1,23 +0,0 @@
-"deploy"
-{
-  "release": "2026.09",
-  "steps": [
-    "build",
-    "test",
-    "smoke-test",
-    "deploy"
-  ],
-  "budget": 19.90
-}
-
-"smoke-test"
-{
-  "budget": 19.9,
-  "release": "2026.09",
-  "steps": [
-    "build",
-    "test",
-    "smoke-test",
-    "deploy"
-  ]
-}

docs/mkdocs/docs/examples/basic_json_document__load.cpp

@@ -1,52 +0,0 @@
-#include <cstdint>
-#include <iostream>
-#include <string>
-#include <vector>
-#include <nlohmann/json_view.hpp>
-
-using json = nlohmann::json;
-using json_document = nlohmann::json_document;
-using image_check = json_document::image_check;
-
-int main()
-{
-    std::cout << std::boolalpha;
-
-    // the image of a parsed document -- as if read back from a cache file or
-    // received from another process running the same build of the library
-    const std::string text = R"({"name": "cache", "note": "caf\u00e9", "replicas": ["db2", "db3"]})";
-    const json_document parsed = json_document::parse(text);
-    const std::vector<std::uint8_t> image = parsed.save();
-
-    // (1)/(2) load() needs no parsing, yet dumps exactly what parsing did
-    const json_document borrowed = json_document::load(image);
-    std::cout << (borrowed.root().dump() == parsed.root().dump()) << '\n';
-    std::cout << borrowed.owns_source() << '\n'; // borrowed: still points into `image`
-
-    // (3) load(std::move(image)) keeps the vector instead of copying it
-    std::vector<std::uint8_t> to_move = image;
-    const json_document owned = json_document::load(std::move(to_move));
-    std::cout << owned.owns_source() << '\n';
-
-    // a damaged image -- the last byte of the decoded string "note" holds
-    // (an escape sequence, so it was unescaped into the document's own
-    // buffer), flipped, as storage or transport corruption might do
-    std::vector<std::uint8_t> damaged = image;
-    damaged[damaged.size() - 2] = 0xFF;
-
-    // image_check::full inspects strings and numbers, so it catches the damage
-    try
-    {
-        static_cast<void>(json_document::load(damaged, image_check::full));
-    }
-    catch (const json::parse_error& e)
-    {
-        std::cout << e.id << '\n';
-    }
-
-    // image_check::bounds only checks structure and bounds, so a cache the
-    // process already trusts loads without the extra scan -- reading a value
-    // the damage did not touch is still safe
-    const json_document trusted = json_document::load(damaged, image_check::bounds);
-    std::cout << trusted.root()["name"].get<std::string>() << '\n';
-}

docs/mkdocs/docs/examples/basic_json_document__load.output

@@ -1,5 +0,0 @@
-true
-false
-true
-116
-cache

docs/mkdocs/docs/examples/basic_json_document__push_back.cpp

@@ -1,24 +0,0 @@
-#include <iostream>
-#include <nlohmann/json_view.hpp>
-
-using json = nlohmann::json;
-using json_editable_document = nlohmann::json_editable_document;
-
-int main()
-{
-    // "events" starts out null -- the first push_back() turns it into an
-    // array, exactly like set() turns a null object member into an object
-    json_editable_document doc = json_editable_document::parse(R"({"source": "sensor-1", "events": null})");
-
-    const auto first = doc.push_back(doc.root()["events"], json{{"type", "start"}, {"t", 0}});
-    for (int t = 1; t <= 3; ++t)
-    {
-        doc.push_back(doc.root()["events"], json{{"type", "tick"}, {"t", t}});
-    }
-
-    // push_back() never moves an existing element: a view taken from an
-    // earlier call still refers to the same element after later ones
-    std::cout << first.dump() << '\n';
-    std::cout << doc.root()["events"].size() << '\n';
-    std::cout << doc.root().dump(2) << '\n';
-}

docs/mkdocs/docs/examples/basic_json_document__push_back.output

@@ -1,23 +0,0 @@
-{"t":0,"type":"start"}
-4
-{
-  "source": "sensor-1",
-  "events": [
-    {
-      "t": 0,
-      "type": "start"
-    },
-    {
-      "t": 1,
-      "type": "tick"
-    },
-    {
-      "t": 2,
-      "type": "tick"
-    },
-    {
-      "t": 3,
-      "type": "tick"
-    }
-  ]
-}

docs/mkdocs/docs/examples/basic_json_document__save.cpp

@@ -1,30 +0,0 @@
-#include <cstdint>
-#include <iostream>
-#include <string>
-#include <vector>
-#include <nlohmann/json_view.hpp>
-
-using json_document = nlohmann::json_document;
-
-int main()
-{
-    std::cout << std::boolalpha;
-
-    // a configuration a service parses once and then caches as an image, so
-    // that later requests can load() it instead of parsing the text again
-    const std::string text = R"({"name": "cache", "host": "db1", "port": 6379, "replicas": ["db2", "db3"]})";
-    const json_document config = json_document::parse(text);
-
-    // save() turns the parsed document into a byte buffer: a 64-byte header,
-    // the node index, the source text, and the decoded strings
-    const std::vector<std::uint8_t> image = config.save();
-    std::cout << image.size() << '\n';
-
-    // the same document always saves to the same bytes
-    std::cout << (image == json_document::parse(text).save()) << '\n';
-
-    // loading the image back needs no parsing, yet dumps exactly what
-    // parsing the text produced
-    const json_document reloaded = json_document::load(image);
-    std::cout << (reloaded.root().dump() == config.root().dump()) << '\n';
-}

docs/mkdocs/docs/examples/basic_json_document__save.output

@@ -1,3 +0,0 @@
-316
-true
-true

docs/mkdocs/docs/examples/basic_json_document__set.cpp

@@ -1,41 +0,0 @@
-#include <iostream>
-#include <nlohmann/json_view.hpp>
-
-using json = nlohmann::json;
-using json_editable_document = nlohmann::json_editable_document;
-using json_editable_view = nlohmann::json_editable_view;
-
-int main()
-{
-    // a configuration file, as it might be read from disk -- "price" is
-    // written with a trailing zero that has no effect on its value
-    const std::string text = R"({
-  "name": "cache",
-  "host": "db1",
-  "port": 6379,
-  "price": 19.90,
-  "replicas": ["db2", "db3"],
-  "timeout": 30
-})";
-
-    json_editable_document doc = json_editable_document::parse(text);
-
-    doc.set(doc.root()["port"], 6380);                    // (1) replace a value
-    doc.set(doc.root(), "region", "us-east");              // (2) add a member
-    doc.set(doc.root()["replicas"], 0, "db4");             // (3) assign an element
-    doc.set(json::json_pointer("/timeout"), 45);           // (4) via a JSON pointer
-
-    // members stay in document order (the new one at the end), and a number
-    // that was not itself edited keeps its exact spelling
-    std::cout << doc.root().dump(2, ' ', false, json_editable_view::number_format::source) << "\n\n";
-
-    // the same edits on a plain json value: object_t is a std::map, so
-    // parsing already sorted the keys, and dump() rewrites every number to
-    // its shortest form, even "price", which was never touched
-    json plain = json::parse(text);
-    plain["port"] = 6380;
-    plain["region"] = "us-east";
-    plain["replicas"][0] = "db4";
-    plain[json::json_pointer("/timeout")] = 45;
-    std::cout << plain.dump(2) << '\n';
-}

docs/mkdocs/docs/examples/basic_json_document__set.output

@@ -1,25 +0,0 @@
-{
-  "name": "cache",
-  "host": "db1",
-  "port": 6380,
-  "price": 19.90,
-  "replicas": [
-    "db4",
-    "db3"
-  ],
-  "timeout": 45,
-  "region": "us-east"
-}
-
-{
-  "host": "db1",
-  "name": "cache",
-  "port": 6380,
-  "price": 19.9,
-  "region": "us-east",
-  "replicas": [
-    "db4",
-    "db3"
-  ],
-  "timeout": 45
-}

docs/mkdocs/docs/examples/bjdata_version_t.cpp

@@ -1,21 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    // an empty binary value is encoded differently by the two drafts:
-    // draft2 omits the optimized type marker for an empty byte array,
-    // while draft3 always writes it
-    json j = json::binary({});
-
-    // encode using BJData draft2 (the default)
-    auto v_draft2 = json::to_bjdata(j, true, true, json::bjdata_version_t::draft2);
-
-    // encode using BJData draft3
-    auto v_draft3 = json::to_bjdata(j, true, true, json::bjdata_version_t::draft3);
-
-    std::cout << "draft2 size: " << v_draft2.size() << '\n'
-              << "draft3 size: " << v_draft3.size() << std::endl;
-}

docs/mkdocs/docs/examples/bjdata_version_t.output

@@ -1,2 +0,0 @@
-draft2 size: 4
-draft3 size: 6

docs/mkdocs/docs/examples/byte_container_with_subtype__container_type.cpp

@@ -1,11 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using byte_container_with_subtype = nlohmann::byte_container_with_subtype<std::vector<std::uint8_t>>;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<byte_container_with_subtype::container_type, std::vector<std::uint8_t>>::value
-              << std::endl;
-}

docs/mkdocs/docs/examples/byte_container_with_subtype__container_type.output

@@ -1 +0,0 @@
-true

docs/mkdocs/docs/examples/byte_container_with_subtype__subtype_type.cpp

@@ -1,10 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using byte_container_with_subtype = nlohmann::byte_container_with_subtype<std::vector<std::uint8_t>>;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<byte_container_with_subtype::subtype_type, std::uint64_t>::value << std::endl;
-}

docs/mkdocs/docs/examples/byte_container_with_subtype__subtype_type.output

@@ -1 +0,0 @@
-true

docs/mkdocs/docs/examples/initializer_list_t.cpp

@@ -1,13 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    // an initializer_list_t is what a braced-init-list of JSON values is deduced as
-    json::initializer_list_t init = {"a", 1, 2.0, false};
-
-    json j(init);
-    std::cout << j.dump() << std::endl;
-}

docs/mkdocs/docs/examples/initializer_list_t.output

@@ -1 +0,0 @@
-["a",1,2.0,false]

docs/mkdocs/docs/examples/json_editable_document.cpp

@@ -1,30 +0,0 @@
-#include <iostream>
-#include <nlohmann/json_view.hpp>
-
-using json = nlohmann::json;
-using json_editable_document = nlohmann::json_editable_document;
-using json_editable_view = nlohmann::json_editable_view;
-
-int main()
-{
-    // a configuration file, as it might be read from disk
-    const std::string text = R"({"name": "cache", "host": "db1", "port": 6379, "price": 19.90})";
-    std::cout << text << "\n\n";
-
-    // patch two fields -- "price" is never touched
-    json_editable_document doc = json_editable_document::parse(text);
-    doc.set(doc.root(), "host", "db2");
-    doc.set(doc.root(), "retries", 3);
-
-    // member order (the new member at the end) and the untouched number's
-    // exact spelling survive
-    std::cout << doc.root().dump(-1, ' ', false, json_editable_view::number_format::source) << '\n';
-
-    // the same patch on a plain json value: keys are sorted (object_t is a
-    // std::map), and "price" is rewritten even though the patch never
-    // touched it
-    json plain = json::parse(text);
-    plain["host"] = "db2";
-    plain["retries"] = 3;
-    std::cout << plain.dump() << '\n';
-}

docs/mkdocs/docs/examples/json_editable_document.output

@@ -1,4 +0,0 @@
-{"name": "cache", "host": "db1", "port": 6379, "price": 19.90}
-
-{"name":"cache","host":"db2","port":6379,"price":19.90,"retries":3}
-{"host":"db2","name":"cache","port":6379,"price":19.9,"retries":3}

docs/mkdocs/docs/examples/json_sax__binary_t.cpp

@@ -1,10 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<json::json_sax_t::binary_t, json::binary_t>::value << std::endl;
-}

docs/mkdocs/docs/examples/json_sax__binary_t.output

@@ -1 +0,0 @@
-true

docs/mkdocs/docs/examples/json_sax__number_float_t.cpp

@@ -1,10 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<json::json_sax_t::number_float_t, json::number_float_t>::value << std::endl;
-}

docs/mkdocs/docs/examples/json_sax__number_float_t.output

@@ -1 +0,0 @@
-true

docs/mkdocs/docs/examples/json_sax__number_integer_t.cpp

@@ -1,10 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<json::json_sax_t::number_integer_t, json::number_integer_t>::value << std::endl;
-}

docs/mkdocs/docs/examples/json_sax__number_integer_t.output

@@ -1 +0,0 @@
-true

docs/mkdocs/docs/examples/json_sax__number_unsigned_t.cpp

@@ -1,10 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<json::json_sax_t::number_unsigned_t, json::number_unsigned_t>::value << std::endl;
-}

docs/mkdocs/docs/examples/json_sax__number_unsigned_t.output

@@ -1 +0,0 @@
-true

docs/mkdocs/docs/examples/json_sax__string_t.cpp

@@ -1,10 +0,0 @@
-#include <iostream>
-#include <nlohmann/json.hpp>
-
-using json = nlohmann::json;
-
-int main()
-{
-    std::cout << std::boolalpha
-              << std::is_same<json::json_sax_t::string_t, json::string_t>::value << std::endl;
-}