Bump Semgrep to 1.182.1 and allow two unfixable advisories

Semgrep 1.168.0 pins pyjwt~=2.13.0, which dependency-review flags (GHSA-ffc3-869f-jxw9 and 14 more). Semgrep 1.182.1 requires pyjwt>=2.15.0; the lock file now has pyjwt 2.15.1, mcp 1.29.0 and click 8.4.2. Semgrep 1.182.1 still pins mcp==1.29.0 (GHSA-84m7-p3x7-pcfv) and opentelemetry-api~=1.37.0 (GHSA-xcq7-p3pf-p88h). Neither code path is used by `semgrep scan` in CI, so dependency-review allows both until Semgrep lifts its pins. Signed-off-by: Niels Lohmann <mail@nlohmann.me>
Pin CI pip installs by hash and update KaTeX/DOMPurify
2026-10-27 00:08:55 +00:00 · 2026-10-23 17:14:25 +02:00 · 2026-10-23 07:20:44 +02:00
611 changed files with 6438 additions and 13431 deletions
@@ -1,33 +1,3 @@
 # Style or vendor rule sets that do not fit a header-only library:
 #   altera-*, fuchsia-*, llvmlibc-*, android-cloexec-fopen, boost-use-ranges, llvm-header-guard,
 #   llvm-include-order, llvm-prefer-static-over-anonymous-namespace, llvm-use-ranges,
 #   misc-use-anonymous-namespace, google-runtime-float, google-runtime-int, hicpp-signed-bitwise,
 #   bugprone-signed-bitwise, hicpp-explicit-conversions, google-explicit-constructor,
 #   cppcoreguidelines-explicit-constructor, misc-explicit-constructor (implicit conversions are the
 #   API), readability-trailing-comma,
 #   hicpp-avoid-goto / cppcoreguidelines-avoid-goto, hicpp-no-array-decay,
 #   hicpp-uppercase-literal-suffix, readability-uppercase-literal-suffix, modernize-use-trailing-return-type.
 # Constructs the library needs on purpose (the library supports C++11 and legacy compilers):
 #   cppcoreguidelines-macro-usage, cppcoreguidelines-avoid-do-while (macros),
 #   cppcoreguidelines-pro-bounds-*, cppcoreguidelines-pro-type-reinterpret-cast,
 #   cppcoreguidelines-pro-type-union-access (parsers, serializers, basic_json's value union),
 #   cppcoreguidelines-avoid-const-or-ref-data-members, cppcoreguidelines-rvalue-reference-param-not-moved,
 #   cppcoreguidelines-avoid-non-const-global-variables, misc-non-private-member-variables-in-classes,
 #   misc-no-recursion (value walks are recursive, bounded by detail::recursion_depth_limit()),
 #   modernize-type-traits, modernize-use-constraints, modernize-use-ranges, modernize-use-std-numbers,
 #   modernize-use-designated-initializers, modernize-use-nodiscard, modernize-concat-nested-namespaces,
 #   readability-redundant-typename, readability-redundant-parentheses,
 #   readability-redundant-access-specifiers, readability-simplify-boolean-expr,
 #   readability-use-concise-preprocessor-directives, modernize-use-string-view,
 #   modernize-use-integer-sign-comparison (needs std::cmp_less; the flagged
 #   static_cast<std::size_t>(end - pos) < n comparisons are deliberate)
 #   (all need a newer standard or compiler than C++11, or would change macro-generated or
 #   deliberately explicit code).
 # Too noisy to be useful (numeric parsing/formatting code, doctest, tests):
 #   bugprone-easily-swappable-parameters, cppcoreguidelines-avoid-magic-numbers, readability-magic-numbers,
 #   readability-identifier-length, readability-function-cognitive-complexity, performance-enum-size,
 #   concurrency-mt-unsafe, misc-confusable-identifiers, misc-include-cleaner (run on its own for
 #   the consumer headers in cmake/ci.cmake).
 # portability-avoid-pragma-once: kept disabled on purpose. #pragma once is accepted
 # by every supported compiler, and tools/amalgamate/amalgamate.py strips it from
 # single_include, so there is nothing left to fix here.
@@ -40,14 +10,14 @@ Checks: '*,
         -android-cloexec-fopen,
         -boost-use-ranges,
         -bugprone-easily-swappable-parameters,
-         -bugprone-signed-bitwise,
+         -cert-err58-cpp,
         -clang-analyzer-webkit.NoUncountedMemberChecker,
         -concurrency-mt-unsafe,
         -cppcoreguidelines-avoid-const-or-ref-data-members,
         -cppcoreguidelines-avoid-do-while,
         -cppcoreguidelines-avoid-goto,
         -cppcoreguidelines-avoid-magic-numbers,
         -cppcoreguidelines-avoid-non-const-global-variables,
         -cppcoreguidelines-explicit-constructor,
         -cppcoreguidelines-macro-usage,
         -cppcoreguidelines-pro-bounds-avoid-unchecked-container-access,
         -cppcoreguidelines-pro-bounds-array-to-pointer-decay,
@@ -56,15 +26,19 @@ Checks: '*,
         -cppcoreguidelines-pro-type-reinterpret-cast,
         -cppcoreguidelines-pro-type-union-access,
         -cppcoreguidelines-rvalue-reference-param-not-moved,
         -cppcoreguidelines-virtual-class-destructor,
         -fuchsia-default-arguments-calls,
         -fuchsia-default-arguments-declarations,
         -fuchsia-overloaded-operator,
         -google-explicit-constructor,
         -google-readability-function-size,
         -google-runtime-float,
         -google-runtime-int,
         -hicpp-avoid-goto,
         -hicpp-explicit-conversions,
         -hicpp-function-size,
         -hicpp-no-array-decay,
         -hicpp-no-assembler,
         -hicpp-signed-bitwise,
         -hicpp-uppercase-literal-suffix,
         -llvm-header-guard,
@@ -74,7 +48,6 @@ Checks: '*,
         -llvmlibc-*,
         -misc-use-anonymous-namespace,
         -misc-confusable-identifiers,
         -misc-explicit-constructor,
         -misc-include-cleaner,
         -misc-no-recursion,
         -misc-non-private-member-variables-in-classes,
@@ -82,22 +55,20 @@ Checks: '*,
         -modernize-type-traits,
         -modernize-use-constraints,
         -modernize-use-designated-initializers,
         -modernize-use-integer-sign-comparison,
         -modernize-use-nodiscard,
         -modernize-use-ranges,
         -modernize-use-string-view,
         -modernize-use-std-numbers,
         -modernize-use-trailing-return-type,
         -performance-enum-size,
         -portability-avoid-pragma-once,
         -readability-function-cognitive-complexity,
         -readability-function-size,
         -readability-identifier-length,
         -readability-magic-numbers,
         -readability-redundant-access-specifiers,
         -readability-redundant-parentheses,
         -readability-redundant-typename,
         -readability-simplify-boolean-expr,
         -readability-trailing-comma,
         -readability-uppercase-literal-suffix,
         -readability-use-concise-preprocessor-directives'
@@ -29,6 +29,13 @@ updates:
      - dependency-name: mermaid
        update-types: ["version-update:semver-major"]
  - package-ecosystem: pip
    directory: /.github/requirements
    schedule:
      interval: daily
    cooldown:
      default-days: 7
  - package-ecosystem: pip
    directory: /tools/astyle
    schedule:
@@ -36,7 +43,7 @@ updates:
    cooldown:
      default-days: 7
    ignore:
-      # astyle is deliberately pinned (see tools/astyle/requirements.txt): newer versions
+      # astyle is deliberately pinned (see tools/astyle/requirements.in): newer versions
      # reformat the code, and the pinned version defines the formatting CI enforces
      - dependency-name: astyle
@@ -0,0 +1 @@
 meson==1.12.1
@@ -0,0 +1,10 @@
 #
 # This file is autogenerated by pip-compile with Python 3.14
 # by the following command:
 #
 #    pip-compile --generate-hashes --no-emit-index-url --output-file=.github/requirements/meson.txt --strip-extras .github/requirements/meson.in
 #
 meson==1.12.1 \
    --hash=sha256:930bc7542cbd9f57009e182fd014eba48cf1a0180a7b9006d2d32d8f168d8b02 \
    --hash=sha256:ab0a6ca09f8ef70c564c8241fb5a23957886a0b53fb58412b5e07eaf07dba743
    # via -r .github/requirements/meson.in
@@ -0,0 +1 @@
 semgrep==1.182.1
@@ -67,10 +67,10 @@ jobs:
      - name: Install astyle
        run: |
          python3 -mvenv venv
-          venv/bin/pip3 install -r $MAIN_DIR/tools/astyle/requirements.txt
+          venv/bin/pip3 install --require-hashes -r $MAIN_DIR/tools/astyle/requirements.txt
      - name: Install generate_natvis dependencies
-        run: pip3 install -r $NATVIS_TOOL_DIR/requirements.txt
+        run: pip3 install --require-hashes -r $MAIN_DIR/tools/generate_natvis/requirements.txt
      - name: Regenerate the tools/macro_builder tables in macro_scope.hpp
        run: |
@@ -31,3 +31,12 @@ jobs:
          persist-credentials: false
      - name: 'Dependency Review'
        uses: actions/dependency-review-action@a1d282b36b6f3519aa1f3fc636f609c47dddb294 # v5.0.0
        with:
          # Semgrep pins mcp==1.29.0 and opentelemetry-api~=1.37.0 exactly
          # (.github/requirements/semgrep.txt), so these cannot be upgraded
          # until Semgrep lifts its pins. They do not apply to our use: CI
          # only runs `semgrep scan` on the checkout and never starts the MCP
          # server (GHSA-84m7-p3x7-pcfv, StreamableHTTP sessions) or parses
          # incoming trace context (GHSA-xcq7-p3pf-p88h, tracestate parsing).
          # Remove the entries once a Semgrep release allows the fixed versions.
          allow-ghsas: GHSA-84m7-p3x7-pcfv, GHSA-xcq7-p3pf-p88h
@@ -43,8 +43,7 @@ jobs:
      - name: flawfinder_scan
        uses: david-a-wheeler/flawfinder@c4216b74cf2639ffa98503768bd6e4299b5440c9 # v2.0.20
        with:
-          # single_include/ is generated from include/ and would report every finding twice
+          arguments: '--sarif ./'
          arguments: "--sarif --exclude '*/single_include/*' ./"
          output: 'flawfinder_results.sarif'
      - name: Upload analysis results to GitHub Security tab
@@ -53,7 +53,7 @@ jobs:
      # SEMGREP_APP_TOKEN is still passed through so registry auth works if a
      # token is ever added.
      - name: Install Semgrep
-        run: python3 -m pip install --user semgrep==1.168.0
+        run: python3 -m pip install --user --require-hashes -r .github/requirements/semgrep.txt
      # `semgrep scan --sarif` always exits 0 even with findings; continue-on-error
      # is a safety net so the SARIF upload still runs if the scan itself errors.
@@ -42,7 +42,7 @@ jobs:
      - name: Check that Meson and pkg-config offer the CMake options
        run: make check_build_options
      - name: Install Meson
-        run: pip install meson
+        run: pip install --require-hashes -r .github/requirements/meson.txt
      - name: Install with Meson
        run: |
          meson setup build-meson --prefix=${{ github.workspace }}/install
@@ -151,7 +151,7 @@ The `json` class provides an API for manipulating a JSON value. To create a `jso
 ```cpp
 #include <fstream>
 #include <nlohmann/json.hpp>
-using nlohmann::json;
+using json = nlohmann::json;
 // ...
@@ -164,7 +164,7 @@ If using modules (enabled with `NLOHMANN_JSON_BUILD_MODULES`), this example beco
 import std;
 import nlohmann.json;
-using nlohmann::json;
+using json = nlohmann::json;
 // ...
@@ -842,7 +842,7 @@ assert(p == p2);
 To make this work with one of your types, you only need to provide two functions:
 ```cpp
-using nlohmann::json;
+using json = nlohmann::json;
 namespace ns {
    void to_json(json& j, const person& p) {
@@ -1257,7 +1257,7 @@ See the page [quality assurance](https://json.nlohmann.me/community/quality_assu
 #include <nlohmann/json.hpp>
 // for convenience
-using nlohmann::json;
+using json = nlohmann::json;
 ```
 to the files you want to process JSON and set the necessary switches to enable C++11 (e.g., `-std=c++11` for GCC and Clang).
@@ -341,14 +341,13 @@ def download(url, docs) -> str:
        raise ValueError(f'not an http(s) URL: {url}')
    req = urllib.request.Request(u.geturl(), headers={'User-Agent': USER_AGENT})
    # (the scheme is checked above)
    # nosemgrep: python.lang.security.audit.dynamic-urllib-use-detected.dynamic-urllib-use-detected
    with urllib.request.urlopen(req, timeout=20) as r:  # nosec B310
        data = r.read()
        ctype = r.headers.get_content_type()
    path = urllib.parse.unquote(u.path).lstrip('/')
    ext = os.path.splitext(path)[1]
    if u.query or not ext or path.endswith('/'):
-        digest = hashlib.sha256(url.encode()).hexdigest()[:12]
+        digest = hashlib.sha1(url.encode(), usedforsecurity=False).hexdigest()[:12]
        path = os.path.join(os.path.dirname(path), digest + CONTENT_TYPE_EXT.get(ctype, ext or '.bin'))
    rel = os.path.normpath(os.path.join('assets', 'external', u.hostname, path))
    out = os.path.join(docs, rel)
@@ -30,14 +30,6 @@ struct adl_serializer {
 - [**from_json**](from_json.md) - convert a JSON value to any value type
 - [**to_json**](to_json.md) - convert any value type to a JSON value
 ## See also
 - [Arbitrary type conversions](../../features/arbitrary_types.md) - how to make your types convertible
 - [**get**](../basic_json/get.md) / [**get_to**](../basic_json/get_to.md) - convert a JSON value to a C++ type
 - [**basic_json**](../basic_json/basic_json.md) - construct a JSON value from a C++ value
 - [**NLOHMANN_DEFINE_TYPE_INTRUSIVE**](../macros/nlohmann_define_type_intrusive.md) - generate the conversion functions for a type
 - [Specializing enum conversion](../../features/enum_conversion.md)
 ## Version history
 - Added in version 2.1.0.
@@ -23,9 +23,6 @@ Checks whether the input is valid JSON.
    respectively as UTF-8, UTF-16, and UTF-32. If `SentinelType` differs from `IteratorType`, it must be comparable to
    the iterator type with `operator!=`.
    Ill-formed UTF-16 and UTF-32 sequences are rejected: a lone surrogate, a high surrogate that is not followed by its
    low surrogate, and a code point above `U+10FFFF` all make this function return `false`.
 Unlike the [`parse()`](parse.md) function, this function neither throws an exception in case of invalid JSON input
 (i.e., a parse error) nor creates diagnostic information.
@@ -38,12 +35,9 @@ Unlike the [`parse()`](parse.md) function, this function neither throws an excep
    - a `#!c FILE` pointer (throws if null)
    - a C-style array of characters
    - a pointer to a null-terminated string of single byte characters (throws if null)
-    - a `std::string` or a `std::string_view` (C++17)
+    - a `std::string`
    - a container `obj` for which `begin(obj)` and `end(obj)` produce a valid pair of iterators
      (as found via ADL or member functions, with semantics compatible to `std::begin` and `std::end`)
    - wide characters (`wchar_t`, `char16_t`, `char32_t`), which are converted to UTF-8: a wide string object
      (`std::wstring`, `std::u16string`, `std::u32string`) or an array (e.g. a wide string literal); a pointer to a
      null-terminated wide string (e.g. `std::u16string::c_str()`) is not supported
 `IteratorType`
 :   a compatible iterator type, for instance.
@@ -131,21 +125,6 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/accept__iterator_pair.output"
    ```
 ??? example "Example: (3) reading from UTF-16 strings"
    The encoding is deduced from the character type of the input. String literals like `u"..."`, `U"..."`, and
    `L"..."` work as well.
    ```cpp
    --8<-- "examples/accept__wide_string.cpp"
    ```
    Output:
    ```json
    --8<-- "examples/accept__wide_string.output"
    ```
 ## See also
 - [parse](parse.md) - deserialize from a compatible input
@@ -172,9 +151,6 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
  ([`JSON_DISABLE_STREAM_BULK_SCAN`](../macros/json_disable_stream_bulk_scan.md)).
 - Parsing from a `FILE*` locks the file once instead of once per character in version 3.13.0
  ([`JSON_DISABLE_UNLOCKED_FILE_IO`](../macros/json_disable_unlocked_file_io.md)).
 - Ill-formed UTF-16 and UTF-32 input (a lone surrogate, a high surrogate that is not followed by its low surrogate, or
  a code point above `U+10FFFF`) is rejected in version 3.13.0; before that, some such sequences were accepted or
  ended the input silently.
 !!! warning "Deprecation"
@@ -90,8 +90,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Constant.
 2. Logarithmic in the size of the container.
 3. Logarithmic in the size of the container.
-4. Linear in the number of reference tokens of `ptr`; for each of them, logarithmic in the size of the object, or
+4. Logarithmic in the size of the container.
   constant for an array.
 ## Notes
@@ -240,8 +239,9 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Added in version 1.0.0.
 2. Added in version 1.0.0.
-3. Added in version 3.11.0. Support for keys convertible to `std::string_view` added in version 3.13.0, consistently
+3. Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept `std::string_view`-convertible keys, as
-   across the lookup functions.
+   already supported by [`operator[]`](operator[].md), [`value`](value.md), [`find`](find.md), and other lookup
   functions.
 4. Added in version 2.0.0. Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) instead of
 [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) for a one-character array index that is not
 a digit (e.g., `/x`) in version 3.13.0, as it already did for longer ones.
@@ -63,4 +63,4 @@ Constant.
 ## Version history
 - Added in version 1.0.0.
- Binary values are supported since version 3.8.0.
+- Adjusted code to return reference to binary values in version 3.8.0.
@@ -482,15 +482,15 @@ basic_json(basic_json&& other) noexcept;
 ## Version history
-1. Added in version 1.0.0.
+1. Since version 1.0.0.
-2. Added in version 1.0.0.
+2. Since version 1.0.0.
-3. Added in version 2.1.0.
+3. Since version 2.1.0.
-4. Added in version 3.1.2. Explicit for different string types if `JSON_USE_IMPLICIT_CONVERSIONS` is `0` since
+4. Since version 3.2.0. Explicit for different string types if `JSON_USE_IMPLICIT_CONVERSIONS` is `0` since
   version 3.13.0.
-5. Added in version 1.0.0.
+5. Since version 1.0.0.
-6. Added in version 1.0.0.
+6. Since version 1.0.0.
-7. Added in version 1.0.0. Fixed in version 3.13.0 to also check the iterator range for binary values; before, a range
+7. Since version 1.0.0. Fixed in version 3.13.0 to also check the iterator range for binary values; before, a range
   that did not cover the whole value (such as `(end(), end())`) was accepted and the whole binary value was copied,
   unlike the other primitive types.
-8. Added in version 1.0.0.
+8. Since version 1.0.0.
-9. Added in version 1.0.0.
+9. Since version 1.0.0.
@@ -61,18 +61,11 @@ Strong exception safety: if an exception occurs, the original value stays intact
 ## Complexity
-1. Logarithmic in the size of the JSON object.
+Logarithmic in the size of the JSON object.
 2. Logarithmic in the size of the JSON object.
 3. At most one lookup per reference token of `ptr`, each logarithmic in the size of the container at that level:
   O(*n* log *m*) for *n* reference tokens and containers of size at most *m*.
 4. Deleted; a call with an integral argument does not compile.
 ## Notes
- Overloads (1) and (2) always return `#!cpp false` when executed on a JSON type that is not an object. Overload (3)
+- This method always returns `#!cpp false` when executed on a JSON type that is not an object.
  also works on arrays and on primitive values: the empty JSON pointer resolves in every JSON value (so
  `#!cpp json(1).contains(""_json_pointer)` returns `#!cpp true`), and `#!cpp json({1, 2}).contains("/1"_json_pointer)`
  returns `#!cpp true`.
 - This method can be executed on any JSON value type.
 - Calling this function with an integer argument (for example, `#!cpp contains(0)`) does not compile: such an argument
  would otherwise implicitly convert to a null `#!cpp const char*` and, from there, cause undefined behavior when
@@ -148,8 +141,9 @@ Strong exception safety: if an exception occurs, the original value stays intact
 ## Version history
 1. Added in version 3.11.0.
-2. Added in version 3.6.0. Extended template `KeyType` to support comparable types in version 3.11.0. Support for keys
+2. Added in version 3.6.0. Extended template `KeyType` to support comparable types in version 3.11.0. Fixed in
-   convertible to `std::string_view` added in version 3.13.0, consistently across the lookup functions.
+   version 3.13.0 to consistently accept `std::string_view`-convertible keys, as already supported by
   [`operator[]`](operator[].md), [`at`](at.md), [`value`](value.md), and other lookup functions.
 3. Added in version 3.7.0.
 4. Deleted overloads for integral key types added in version 3.13.0 to reject such calls at compile time instead of
   causing undefined behavior at runtime.
@@ -92,7 +92,8 @@ Logarithmic in the size of the JSON object.
 ## Version history
 1. Added in version 3.11.0.
-2. Added in version 1.0.0. Changed to support comparable key types in version 3.11.0. Support for keys convertible to
+2. Added in version 1.0.0. Changed parameter `key` type to `KeyType&&` in version 3.11.0. Fixed in version 3.13.0 to
-   `std::string_view` added in version 3.13.0, consistently across the lookup functions.
+   consistently accept `std::string_view`-convertible keys, as already supported by [`operator[]`](operator[].md),
   [`at`](at.md), [`value`](value.md), and other lookup functions.
 3. Deleted overload for integral key types added in version 3.13.0 to reject such calls at compile time instead of
   causing undefined behavior at runtime.
@@ -2,27 +2,17 @@
 ```cpp
 static basic_json diff(const basic_json& source,
-                       const basic_json& target,
+                       const basic_json& target);
                       const string_t& path = "");
 ```
 Creates a [JSON Patch](http://jsonpatch.com) so that value `source` can be changed into the value `target` by calling
 [`patch`](patch.md) function.
-For two JSON values `source` and `target`, the following code yields `#!cpp true`:
+For two JSON values `source` and `target`, the following code always yields `#!cpp true`:
 ```cpp
 source.patch(diff(source, target)) == target;
 ```
 The equality holds up to [`operator==`](operator_eq.md), so it has the following exceptions:
 - A value that is not equal to itself cannot round-trip. This applies to `NaN` (also nested in an array or object) and
  to [discarded](is_discarded.md) values: `diff` emits a `replace` operation for them. A `NaN` in the patch is
  serialized as `#!json null`, so a patch that was dumped and parsed again would set `#!json null`.
 - Numbers that compare equal produce no operation, even if their types or signs differ: `diff(1, 1.0)`,
  `diff(1u, 1)` (unsigned and signed integer) and `diff(0.0, -0.0)` all return `#!json []`. The patched value is then
  the `source` and keeps its number type.
 ## Parameters
 `source` (in)
@@ -31,12 +21,6 @@ The equality holds up to [`operator==`](operator_eq.md), so it has the following
 `target` (in)
 :   JSON value to compare against
 `path` (in)
 :   a prefix that is put verbatim in front of the `path` member of every operation (default: `""`, which addresses the
    root of the value). The prefix is neither escaped nor validated: `#!cpp diff(1, 2, "abc")` yields an operation with
    the `path` `abc`, which is not a valid JSON Pointer. Use it with a valid JSON Pointer such as `/root` and escape
    `~` and `/` in its reference tokens (see [JSON Pointer](../../features/json_pointer.md)).
 ## Return value
 a JSON patch to convert the `source` to `target`
@@ -47,32 +31,11 @@ Strong guarantee: `source` and `target` are never modified.
 ## Complexity
-Linear in the total number of values (including nested ones) in `source` and `target`, times the cost of a key-based
+Linear in the lengths of `source` and `target`.
 object operation (looking up a key in an object): logarithmic for [`json`](../json.md), and linear for
 [`ordered_json`](../ordered_json.md) (see [`ordered_map` complexity](../ordered_map.md#complexity)). For
 `ordered_json`, diffing two objects with `n` and `m` members therefore takes O((n+m)²) when their keys do not line up
 (e.g., a key was added or the keys are in a different order). The size of the patch is proportional to the number of
 operations times the length of their paths, so a small change deep inside a value yields a long `path`.
 ## Notes
- Currently, only `remove`, `add`, and `replace` operations are generated.
+Currently, only `remove`, `add`, and `replace` operations are generated.
 - The patch is correct, but not guaranteed to be minimal. For instance, `diff([1,2,3], [0,1,2,3])` yields three
  `replace` operations and one `add` operation instead of a single insertion.
 - Differences between two arrays are reported index by index. Elements that were added at the end of the array are added
  with `add` operations on the path `/-` (appended in order), and elements that were removed are removed with `remove`
  operations from the highest index down to the lowest, so that the remaining indices stay valid.
 - For objects, the operations for the members of `source` come first (`replace`, `remove`, or the operations for nested
  values, in the iteration order of `source`), followed by `add` operations for the members that only `target` has.
 - For [`ordered_json`](../ordered_json.md), objects with the same keys in a different order are different. As a patch
  cannot reorder members, `diff` removes all keys of the `source` object and adds them again in the order of the
  `target`.
 - If `source` and `target` differ as a whole (e.g., different types), the patch consists of a single `replace`
  operation for the root of the value, i.e., with the `path` `""` (or the given `path` prefix).
 - The `value` members of the patch hold copies of values of `target`. A [binary](../../features/binary_values.md) value
  has no JSON representation: when a patch that contains one is serialized, it becomes an object such as
  `#!json {"bytes":[1,3],"subtype":null}`, so a parsed patch no longer holds a binary value (and would set that object
  instead).
 ## Examples
@@ -69,6 +69,6 @@ Logarithmic in the size of the container, O(log(`size()`)).
 ## Version history
- Added in version 2.0.8.
+- Since version 2.0.8.
 - Fixed in version 3.13.0: for [`ordered_json`](../ordered_json.md), the value could previously only be passed as an
  rvalue; it can now also be passed as an lvalue or a `#!cpp const` lvalue, matching the behavior of `json`.
@@ -67,5 +67,5 @@ Amortized constant.
 ## Version history
- Added in version 2.0.8.
+- Since version 2.0.8.
 - Returns reference since 3.7.0.
@@ -213,6 +213,7 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Added in version 1.0.0. Added support for binary types in version 3.8.0.
 2. Added in version 1.0.0. Added support for binary types in version 3.8.0.
 3. Added in version 1.0.0.
-4. Added in version 3.11.0. Support for keys convertible to `std::string_view` added in version 3.13.0, consistently
+4. Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept `std::string_view`-convertible keys, as
-   across the lookup functions.
+   already supported by [`operator[]`](operator[].md), [`at`](at.md), [`value`](value.md), and other lookup
   functions.
 5. Added in version 1.0.0.
@@ -84,4 +84,4 @@ constructor.
 ## Version history
- Added in version 3.0.0.
+- Since version 3.0.0.
@@ -99,7 +99,8 @@ Logarithmic in the size of the JSON object.
 ## Version history
 1. Added in version 3.11.0.
-2. Added in version 1.0.0. Changed to support comparable types in version 3.11.0. Support for keys convertible to
+2. Added in version 1.0.0. Changed to support comparable types in version 3.11.0. Fixed in version 3.13.0 to
-   `std::string_view` added in version 3.13.0, consistently across the lookup functions.
+   consistently accept `std::string_view`-convertible keys, as already supported by [`operator[]`](operator[].md),
   [`at`](at.md), [`value`](value.md), and other lookup functions.
 3. Deleted overloads for integral key types added in version 3.13.0 to reject such calls at compile time instead of
   causing undefined behavior at runtime.
@@ -57,4 +57,4 @@ Constant.
 ## Version history
 - Added in version 1.0.0.
- Binary values are supported since version 3.8.0.
+- Adjusted code to return reference to binary values in version 3.8.0.
@@ -188,6 +188,6 @@ overload (3).
 ## Version history
-1. Added in version 2.1.0.
+1. Since version 2.1.0.
-2. Added in version 2.1.0. Extended to work with other specializations of `basic_json` in version 3.1.2.
+2. Since version 2.1.0. Extended to work with other specializations of `basic_json` in version 3.2.0.
-3. Added in version 1.0.0.
+3. Since version 1.0.0.
@@ -45,7 +45,7 @@ Constant.
    #include <iostream>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -76,5 +76,5 @@ Depends on the `json_serializer<ValueType>::from_json()` implementation.
 ## Version history
- Added in version 3.3.0.
+- Since version 3.3.0.
 - Added a `static_assert` with a clear message for `const` arguments in version 3.13.0.
@@ -44,22 +44,6 @@ are collected in [Template Parameter Requirements](../../features/types/template
 - [**json**](../json.md) - default specialization
 - [**ordered_json**](../ordered_json.md) - a specialization that maintains the insertion order of object keys
 ## Documents and views
 Besides `basic_json`, the library offers a second way to hold a parsed JSON text: a
 [`basic_json_document`](../basic_json_document/index.md), which owns or borrows the text and holds a flat index of the
 values in it, and a [`basic_json_view`](../basic_json_view/index.md), a read-only handle to one value of such a document.
 Both are defined in the header `<nlohmann/json_view.hpp>`; see
 [Zero-copy JSON views](../../features/json_view.md) for the concept and the trade-offs.
 - [**json_document**](../json_document.md) / [**ordered_json_document**](../ordered_json_document.md) - read-only
  documents of the `basic_json` specialization they belong to
 - [**json_editable_document**](../json_editable_document.md) /
  [**ordered_json_editable_document**](../ordered_json_editable_document.md) - documents that can be modified in place
 - [**json_view**](../json_view.md) / [**ordered_json_view**](../ordered_json_view.md) - views of a document
 - [**json_editable_view**](../json_editable_view.md) /
  [**ordered_json_editable_view**](../ordered_json_editable_view.md) - views of an editable document
 ## Iterator invalidation
 All operations that add values to an **array** ([`push_back`](push_back.md) , [`operator+=`](operator+=.md),
@@ -359,9 +343,6 @@ Access to the JSON value
 ## See also
 - [RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format](https://tools.ietf.org/html/rfc8259)
 - [basic_json_document](../basic_json_document/index.md) / [basic_json_view](../basic_json_view/index.md) - parse a JSON
  text into a flat index and read it through a view
 - [Zero-copy JSON views](../../features/json_view.md) - when to use a document and a view instead of a `basic_json`
 ## Version history
@@ -75,4 +75,4 @@ classDiagram
 ## Version history
- Added in version 3.0.0.
+- Since version 3.0.0.
@@ -104,8 +104,8 @@ When iterating over an array, `key()` will return the index of the element as st
 ## Version history
- Added in version 3.1.0 as the replacement of the static function `iterator_wrapper`, which was available since
+- Added `iterator_wrapper` in version 3.0.0.
-  version 1.0.0 and is deprecated since version 3.1.0.
+- Added `items` and deprecated `iterator_wrapper` in version 3.1.0.
 - Added structured binding support in version 3.5.0.
 !!! warning "Deprecation"
@@ -51,4 +51,4 @@ deserializes. See [Template Parameter Requirements](../../features/types/templat
 ## Version history
- Added in version 2.1.0.
+- Since version 2.0.0.
@@ -39,33 +39,13 @@ Basic guarantee: if an exception is thrown during the operation, the JSON value
 ## Complexity
-Linear in the total number of values (including nested ones) in `apply_patch`, times the cost of a key-based object
+Linear in the lengths of `apply_patch`.
 operation (looking up, adding, or erasing a member): logarithmic for [`json`](../json.md), and linear for
 [`ordered_json`](../ordered_json.md) (see [`ordered_map` complexity](../ordered_map.md#complexity)). For
 `ordered_json`, patching an object that has `n` members with a patch that has `m` members therefore takes O(n·m). The
 cost also includes one copy of `apply_patch` (see the notes below).
 ## Notes
- `apply_patch` may be `#!cpp *this` itself or refer to a value contained in `#!cpp *this` (for example, a subobject
+`apply_patch` may be `#!cpp *this` itself or refer to a value contained in `#!cpp *this` (for example, a subobject
-  returned by `#!cpp (*this)[key]`); it is read as it was when `merge_patch()` was called, before any modification of
+returned by `#!cpp (*this)[key]`); it is read as it was when `merge_patch()` was called, before any modification of
-  `#!cpp *this`. To make this possible, the function copies `apply_patch` before it modifies `#!cpp *this`, so the cost
+`#!cpp *this`.
  includes one copy of the patch.
 - A merge patch uses `#!json null` to remove a member, so it cannot set a member to `#!json null`: applying
  `#!json {"a":null}` to `#!json {"a":1}` gives `#!json {}`.
 - Arrays are not merged: an array in the patch replaces the target value as a whole, and a `#!json null` inside an
  array is kept as an element. `#!json null` members of the target that the patch does not mention are preserved.
 - A `#!json null` in the patch only removes a member; it does not prevent the creation of the enclosing objects.
  Applying `#!json {"a":{"b":null}}` to `#!json {}` gives `#!json {"a":{}}` (see example 15 in Appendix A of the RFC).
 - If `apply_patch` is not an object, it replaces the target as a whole. In particular, a `#!json null` patch turns the
  target into `#!json null`. If `apply_patch` is an object and the target is not, the target is first replaced by an
  empty object, so applying `#!json {}` to `#!json 1` gives `#!json {}`.
 - A merge patch cannot express every change; for example, it cannot reorder array elements or remove a specific array
  element. Use [JSON Patch](../../features/json_patch.md) ([RFC 6902](https://tools.ietf.org/html/rfc6902)) for that.
  [`merge_diff`](merge_diff.md) has a matching limitation, see its notes.
 - A [discarded](is_discarded.md) value is treated like any other non-object value: a discarded
  `apply_patch` turns the target into a discarded value, and an object patch replaces a discarded target by an object
  as described above.
 ## Examples
@@ -91,6 +71,6 @@ cost also includes one copy of `apply_patch` (see the notes below).
 ## Version history
- Added in version 3.1.0.
+- Added in version 3.0.0.
 - Fixed use of freed or relocated memory when `apply_patch` is `#!cpp *this` or refers to a value contained in
  `#!cpp *this`, in version 3.13.0.
@@ -128,6 +128,6 @@ interpreted as `object_t::value_type` or `std::initializer_list<basic_json>`, se
 ## Version history
-1. Added in version 1.0.0.
+1. Since version 1.0.0.
-2. Added in version 1.0.0.
+2. Since version 1.0.0.
-3. Added in version 2.0.0.
+3. Since version 2.0.0.
@@ -92,20 +92,12 @@ Strong exception safety: if an exception occurs, the original value stays intact
    For the **const** version, an object key or array index in `ptr` that does not exist is not reported by an
    exception, but is undefined behavior (see the notes below). Use [`at`](at.md) for checked access.
    If the **non-const** version throws, the value is left unchanged: values it created for earlier reference tokens
    of `ptr` are removed again. This also holds for exceptions such as `#!cpp std::bad_alloc` or
    `#!cpp std::length_error` thrown while padding an array up to a very large index. With custom
    [template parameters](../../features/types/template_parameters.md), this requires that `erase()` of the object and
    array types and the move operations of the custom base class do not throw.
 ## Complexity
 1. Constant if `idx` is in the range of the array. Otherwise, linear in `idx - size()`.
 2. Logarithmic in the size of the container.
 3. Logarithmic in the size of the container.
-4. Linear in the number of reference tokens of `ptr`; for each of them, logarithmic in the size of the object, or
+4. Logarithmic in the size of the container.
   constant for an array. When the non-const version pads an array with `#!json null` values, it is additionally
   linear in `idx - size()` for that array.
 ## Notes
@@ -145,21 +137,10 @@ Strong exception safety: if an exception occurs, the original value stays intact
        When the JSON pointer traverses intermediate levels that don't exist at all yet (not just a missing
        leaf), each missing level is created as an array or an object depending on whether the corresponding
-        pointer token is a valid array index: the token `0`, a sequence of digits that does not begin with `0`,
+        pointer token parses as a non-negative integer: a numeric token creates an array, a non-numeric token
-        or the token `-` creates an array, and every other token creates an object. For example, on an
+        creates an object. For example, on an initially `#!json null` value, `/foo/0/0/0` creates nested arrays,
-        initially `#!json null` value, `/foo/0/0/0` creates nested arrays, while `/foo/one/one/one` creates
+        while `/foo/one/one/one` creates nested objects. This is not specified by the JSON Pointer RFC; it is
-        nested objects. Tokens such as `01` or the empty token cannot be array indices (cf. RFC 6901, Sect. 4)
+        this library's own, intentional disambiguation rule. See also [JSON Pointer](../../features/json_pointer.md).
        and therefore create objects, just as they would if the level already existed as an object. This is not
        specified by the JSON Pointer RFC; it is this library's own, intentional disambiguation rule. See also
        [JSON Pointer](../../features/json_pointer.md).
    !!! warning "Large array indices"
        As the array is filled up with `#!json null` values to the given index, the memory used grows with the index
        and not with the size of the pointer: on a 64-bit platform, the index `10000000` allocates about 160 MB.
        The library does not limit the index, so check the array indices of a JSON pointer from untrusted input
        before using it with the non-const version. See
        [Parsing untrusted input](../../features/parsing/untrusted_input.md#json-pointers-and-flattened-keys).
 !!! warning "Deprecation"
@@ -303,13 +284,11 @@ Strong exception safety: if an exception occurs, the original value stays intact
 1. Added in version 1.0.0. Fixed in version 3.13.0 to throw `#!cpp std::length_error` instead of emptying the array and
   accessing it out of bounds when `idx` equals the maximum value of `size_type`. A missing index in the const version
   is guarded by a runtime assertion since version 3.13.0.
-2. Added in version 1.0.0. Added overloads for `T* key` in version 1.1.0. The `T* key` overloads forward to
+2. Added in version 1.0.0. Added overloads for `T* key` in version 1.1.0. Removed overloads for `T* key` (replaced by 3)
-   overload 3 since version 3.11.0.
+   in version 3.11.0.
-3. Added in version 3.11.0. Support for keys convertible to `std::string_view` added in version 3.13.0, consistently
+3. Added in version 3.11.0. Fixed in version 3.13.0 to consistently accept `std::string_view`-convertible keys, as
-   across the lookup functions.
+   already supported by [`at`](at.md), [`value`](value.md), [`find`](find.md), and other lookup functions.
 4. Added in version 2.0.0. A missing array index in the const version is guarded by a runtime assertion since
   version 3.13.0. Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) instead of
 [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) for a one-character array index that is not
-a digit (e.g., `/x`) in version 3.13.0, as it already did for longer ones. Fixed in version 3.13.0 to leave the value
+a digit (e.g., `/x`) in version 3.13.0, as it already did for longer ones.
 unchanged if the non-const version throws (strong exception safety, as documented); before, values created for earlier
 reference tokens of `ptr` were kept.
@@ -89,6 +89,6 @@ Linear in the size of the JSON value.
 ## Version history
- Added in version 1.0.0.
+- Since version 1.0.0.
 - Macros `JSON_EXPLICIT`/[`JSON_USE_IMPLICIT_CONVERSIONS`](../macros/json_use_implicit_conversions.md) added
  in version 3.9.0.
@@ -75,4 +75,4 @@ classDiagram
 ## Version history
- Added in version 3.0.0.
+- Since version 3.0.0.
@@ -76,4 +76,4 @@ classDiagram
 ## Version history
- Added in version 3.0.0.
+- Since version 3.0.0.
@@ -25,10 +25,6 @@ static basic_json parse(IteratorType first, SentinelType last,
    respectively as UTF-8, UTF-16, and UTF-32. If `SentinelType` differs from `IteratorType`, it must be comparable to
    the iterator type with `operator!=`.
    Ill-formed UTF-16 and UTF-32 sequences are rejected: a lone surrogate, a high surrogate that is not followed by its
    low surrogate, and a code point above `U+10FFFF` all yield a
    [`parse_error.101`](../../home/exceptions.md#jsonexceptionparse_error101).
 ## Template parameters
 `InputType`
@@ -38,12 +34,9 @@ static basic_json parse(IteratorType first, SentinelType last,
    - a `FILE` pointer (throws if null)
    - a C-style array of characters
    - a pointer to a null-terminated string of single byte characters (throws if null)
-    - a `std::string` or a `std::string_view` (C++17)
+    - a `std::string`
    - a container `obj` for which `begin(obj)` and `end(obj)` produce a valid pair of iterators
      (as found via ADL or member functions, with semantics compatible to `std::begin` and `std::end`)
    - wide characters (`wchar_t`, `char16_t`, `char32_t`), which are converted to UTF-8: a wide string object
      (`std::wstring`, `std::u16string`, `std::u32string`) or an array (e.g. a wide string literal); a pointer to a
      null-terminated wide string (e.g. `std::u16string::c_str()`) is not supported
 `IteratorType`
 :   a compatible iterator type, for instance.
@@ -119,13 +112,6 @@ By default, a `'\0'` (NUL) byte anywhere in the input is treated as end of input
 outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-bytes-in-the-input) for details and the
 [`JSON_STRICT_NUL_HANDLING`](../macros/json_strict_nul_handling.md) macro to opt into rejecting it instead.
 !!! tip "Parsing into a document instead of a value"
    [`basic_json_document::parse`](../basic_json_document/parse.md) accepts the same inputs and the same options, but
    keeps the result as a flat index of the parsed values instead of a tree of `basic_json` values. It is faster and uses
    less memory when only parts of the document are read, and it also accepts a pointer to a null-terminated wide string,
    which `parse()` does not. See [Zero-copy JSON views](../../features/json_view.md).
 !!! tip "Performance"
    Contiguous inputs (strings, string views, vectors, arrays, pointer ranges) are the fastest to parse. A
@@ -264,22 +250,6 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
    --8<-- "examples/trailing_commas.output"
    ```
 ??? example "Example: parse from UTF-16, UTF-32, and wide strings"
    The encoding is deduced from the character type of the input; `std::u16string` and `std::u32string` are interpreted
    as UTF-16 and UTF-32, and `std::wstring` uses the platform's `wchar_t` width. String literals like `u"..."`,
    `U"..."`, and `L"..."` work as well, as do iterators over wide characters.
    ```cpp
    --8<-- "examples/parse__wide_string.cpp"
    ```
    Output:
    ```json
    --8<-- "examples/parse__wide_string.output"
    ```
 ## See also
 - [accept](accept.md) - check if the input is valid JSON
@@ -310,9 +280,6 @@ outside of a string, invalid) byte; see the [FAQ entry](../../home/faq.md#nul-by
  time).
 - Parsing from a `FILE*` locks the file once instead of once per character in version 3.13.0
  ([`JSON_DISABLE_UNLOCKED_FILE_IO`](../macros/json_disable_unlocked_file_io.md) restores `std::fgetc`).
 - Ill-formed UTF-16 and UTF-32 input (a lone surrogate, a high surrogate that is not followed by its low surrogate, or
  a code point above `U+10FFFF`) is rejected with `parse_error.101` in version 3.13.0; before that, some such
  sequences were accepted or ended the input silently.
 !!! warning "Deprecation"
@@ -84,4 +84,4 @@ or the end of file. This also holds true when reading a byte vector for binary f
 ## Version history
- Added in version 3.0.0.
+- Since version 3.0.0.
@@ -40,7 +40,7 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
  where an existing element is required (the "path" of "replace", the "from" of "move" and "copy"); example:
  `"array index '-' (3) is out of range"`.
 - Throws [`out_of_range.403`](../../home/exceptions.md#jsonexceptionout_of_range403) if a JSON pointer inside the patch
-  could not be resolved successfully in the current JSON value; example: `"key 'baz' not found"`.
+  could not be resolved successfully in the current JSON value; example: `"key baz not found"`.
 - Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a reference token of a JSON
  pointer inside the patch cannot be resolved, e.g., `-` in a "remove" operation or `1a` for an array; example:
  `"unresolved reference token '-'"`.
@@ -53,10 +53,7 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [`out_of_range.414`](../../home/exceptions.md#jsonexceptionout_of_range414) if a "move" operation's "from"
  location is a proper prefix of its "path" location.
 - Throws [`other_error.501`](../../home/exceptions.md#jsonexceptionother_error501) if "test" operation was
-  unsuccessful. A "test" operation whose "path" does not exist is unsuccessful, too: the failed lookup is reported as a
+  unsuccessful.
  failed test, even if the operation has no "value" member (which would otherwise be
  [`parse_error.105`](../../home/exceptions.md#jsonexceptionparse_error105)). Which of the two errors is reported for
  this combination depends on the order in which the operands of a comparison are evaluated, so do not rely on it.
 ## Complexity
@@ -68,10 +65,6 @@ the JSON value, the complexity can usually be neglected.
 The application of a patch is atomic: Either all operations succeed and the patched document is returned or an exception
 is thrown. In any case, the original value is not changed: the patch is applied to a copy of the value.
 Duplicate member names inside an operation object are resolved by the parser before the patch is applied (the last one
 is kept, see [`object_t`](object_t.md#behavior)), so `#!json {"op": "add", "op": "remove", "path": "/a"}` is a
 `remove` operation.
 ## Examples
 ??? example "Example: apply a JSON patch"
@@ -115,7 +108,6 @@ is kept, see [`object_t`](object_t.md#behavior)), so `#!json {"op": "add", "op":
 - Added in version 2.0.0.
 - Added [`out_of_range.411`](../../home/exceptions.md#jsonexceptionout_of_range411) and stopped relying on an internal assertion when an "add" operation's
  target location has a non-object/non-array parent in version 3.13.0.
  This includes a `null` parent, which was previously silently converted to an object, in version 3.13.0.
 - Added [`out_of_range.413`](../../home/exceptions.md#jsonexceptionout_of_range413) and stopped silently ignoring a "remove" operation whose target
  location has a non-object/non-array parent in version 3.13.0.
 - Added [`out_of_range.414`](../../home/exceptions.md#jsonexceptionout_of_range414) and rejected a "move" operation whose "from" location is a proper
@@ -36,7 +36,7 @@ No guarantees, value may be corrupted by an unsuccessful patch operation.
  where an existing element is required (the "path" of "replace", the "from" of "move" and "copy"); example:
  `"array index '-' (3) is out of range"`.
 - Throws [`out_of_range.403`](../../home/exceptions.md#jsonexceptionout_of_range403) if a JSON pointer inside the patch
-  could not be resolved successfully in the current JSON value; example: `"key 'baz' not found"`.
+  could not be resolved successfully in the current JSON value; example: `"key baz not found"`.
 - Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a reference token of a JSON
  pointer inside the patch cannot be resolved, e.g., `-` in a "remove" operation or `1a` for an array; example:
  `"unresolved reference token '-'"`.
@@ -49,10 +49,7 @@ No guarantees, value may be corrupted by an unsuccessful patch operation.
 - Throws [`out_of_range.414`](../../home/exceptions.md#jsonexceptionout_of_range414) if a "move" operation's "from"
  location is a proper prefix of its "path" location.
 - Throws [`other_error.501`](../../home/exceptions.md#jsonexceptionother_error501) if "test" operation was
-  unsuccessful. A "test" operation whose "path" does not exist is unsuccessful, too: the failed lookup is reported as a
+  unsuccessful.
  failed test, even if the operation has no "value" member (which would otherwise be
  [`parse_error.105`](../../home/exceptions.md#jsonexceptionparse_error105)). Which of the two errors is reported for
  this combination depends on the order in which the operands of a comparison are evaluated, so do not rely on it.
 ## Complexity
@@ -65,10 +62,6 @@ Unlike [`patch`](patch.md), `patch_inplace` applies the operation "in place" and
 That makes it faster for large documents by avoiding the copy. However, the JSON value might be corrupted if the
 function throws an exception.
 Duplicate member names inside an operation object are resolved by the parser before the patch is applied (the last one
 is kept, see [`object_t`](object_t.md#behavior)), so `#!json {"op": "add", "op": "remove", "path": "/a"}` is a
 `remove` operation.
 ## Examples
 ??? example "Example: apply a JSON patch in place"
@@ -113,7 +106,6 @@ is kept, see [`object_t`](object_t.md#behavior)), so `#!json {"op": "add", "op":
 - Added in version 3.11.0.
 - Added [`out_of_range.411`](../../home/exceptions.md#jsonexceptionout_of_range411) and stopped relying on an internal assertion when an "add" operation's
  target location has a non-object/non-array parent in version 3.13.0.
  This includes a `null` parent, which was previously silently converted to an object, in version 3.13.0.
 - Added [`out_of_range.413`](../../home/exceptions.md#jsonexceptionout_of_range413) and stopped silently ignoring a "remove" operation whose target
  location has a non-object/non-array parent in version 3.13.0.
 - Added [`out_of_range.414`](../../home/exceptions.md#jsonexceptionout_of_range414) and rejected a "move" operation whose "from" location is a proper
@@ -125,6 +125,6 @@ throws.
 ## Version history
-1. Added in version 1.0.0.
+1. Since version 1.0.0.
-2. Added in version 1.0.0.
+2. Since version 1.0.0.
-3. Added in version 2.0.0.
+3. Since version 2.0.0.
@@ -31,10 +31,6 @@ Read from input and generate SAX events
    respectively as UTF-8, UTF-16, and UTF-32. If `SentinelType` differs from `IteratorType`, it must be comparable to
    the iterator type with `operator!=`.
    Ill-formed UTF-16 and UTF-32 sequences are rejected: a lone surrogate, a high surrogate that is not followed by its
    low surrogate, and a code point above `U+10FFFF` all yield a
    [`parse_error.101`](../../home/exceptions.md#jsonexceptionparse_error101).
 The SAX event lister must follow the interface of [`json_sax`](../json_sax/index.md).
 ## Template parameters
@@ -46,12 +42,8 @@ The SAX event lister must follow the interface of [`json_sax`](../json_sax/index
    - a `FILE` pointer
    - a C-style array of characters
    - a pointer to a null-terminated string of single byte characters
    - a `std::string` or a `std::string_view` (C++17)
    - a container `obj` for which `begin(obj)` and `end(obj)` produce a valid pair of iterators
      (as found via ADL or member functions, with semantics compatible to `std::begin` and `std::end`)
    - wide characters (`wchar_t`, `char16_t`, `char32_t`), which are converted to UTF-8: a wide string object
      (`std::wstring`, `std::u16string`, `std::u32string`) or an array (e.g. a wide string literal); a pointer to a
      null-terminated wide string (e.g. `std::u16string::c_str()`) is not supported
 `IteratorType`
 :   a compatible iterator type for overload (2); a pair of character iterators whose `value_type` is an integral type
@@ -168,9 +160,6 @@ use the same file with stdio functions, but it must not wait for another thread
  ([`JSON_DISABLE_STREAM_BULK_SCAN`](../macros/json_disable_stream_bulk_scan.md)).
 - Parsing from a `FILE*` locks the file once instead of once per character in version 3.13.0
  ([`JSON_DISABLE_UNLOCKED_FILE_IO`](../macros/json_disable_unlocked_file_io.md)).
 - Ill-formed UTF-16 and UTF-32 input (a lone surrogate, a high surrogate that is not followed by its low surrogate, or
  a code point above `U+10FFFF`) is rejected with `parse_error.101` in version 3.13.0; before that, some such
  sequences were accepted or ended the input silently.
 !!! warning "Deprecation"
@@ -182,10 +182,10 @@ Constant.
 ## Version history
-1. Added in version 1.0.0. Exchanges the `json_base_class_t` subobject along with the value since version 3.13.0.
+1. Since version 1.0.0. Exchanges the `json_base_class_t` subobject along with the value since version 3.13.0.
-2. Added in version 1.0.0. Exchanges the `json_base_class_t` subobject along with the value since version 3.13.0.
+2. Since version 1.0.0. Exchanges the `json_base_class_t` subobject along with the value since version 3.13.0.
-3. Added in version 1.0.0.
+3. Since version 1.0.0.
-4. Added in version 1.0.0.
+4. Since version 1.0.0.
-5. Added in version 1.0.0.
+5. Since version 1.0.0.
-6. Added in version 3.8.0.
+6. Since version 3.8.0.
-7. Added in version 3.8.0.
+7. Since version 3.8.0.
@@ -124,3 +124,5 @@ 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 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.
@@ -76,4 +76,4 @@ classDiagram
 ## Version history
- Added in version 3.0.0.
+- Since version 3.0.0.
@@ -36,9 +36,9 @@ The function can throw the following exceptions:
 - Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) if an array index in a key is not a
  number; example: `"array index 'one' is not a number"`
 - Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a level becomes an array
-  (because one of its keys is `0`) and another key at that level is empty (as in `/a/`), is `-`, or begins with a digit
+  (because one of its keys is `0`) and another key at that level begins with a digit but is not a valid array index
-  but is not a valid array index (such as `1a`); examples: `"unresolved reference token '-'"`,
+  (such as `1a`), or is `-`; example:
-  `"unresolved reference token ''"`
+  `"unresolved reference token '-'"`
 ## Complexity
@@ -46,7 +46,7 @@ Linear in the size of the JSON value.
 ## Notes
-Empty objects and arrays are flattened by [`flatten()`](flatten.md) to `#!json null` values and cannot be unflattened to
+Empty objects and arrays are flattened by [`flatten()`](flatten.md) to `#!json null` values and cannot unflattened to
 their original type.
 A flattened array and a flattened object whose keys are array indices are indistinguishable, because both are
@@ -54,12 +54,7 @@ described by the same JSON pointers. A value is therefore restored as an array i
 reference token `0`, and as an object otherwise: `#!json {"2": 1}` is restored unchanged, whereas `#!json {"0": 1}` is
 restored as `#!json [1]`. This decision does not depend on the order in which the flattened object is iterated.
-A third case is an object that has the key `0` next to a key that is not a valid array index: `#!json {"0": 1, "b": 2}`
+Apart from these two cases, for a JSON value `j`, the following is always true:
 is flattened to `#!json {"/0": 1, "/b": 2}`, and unflatten treats the level as an array and throws
 [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) because `b` is not a number. (For the keys
 `-`, `1a`, or the empty key instead of `b`, it throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404).)
 Apart from these three cases, for a JSON value `j`, the following is always true:
 `#!cpp j == j.flatten().unflatten()`.
 ## Examples
@@ -45,9 +45,6 @@ This is equivalent to Python's `dict.get(key, default)`.
       return default_value;
    }
    ```
    with one exception: if the JSON value is neither an array nor an object, the function throws
    [`type_error.306`](../../home/exceptions.md#jsonexceptiontype_error306) before looking at `ptr`, even for the empty
    pointer, whereas `at` returns the value itself for the empty pointer.
 !!! note "Differences to `at` and `operator[]`"
@@ -234,8 +231,11 @@ changes to any JSON value.
 1. Added in version 1.0.0. Changed parameter `default_value` type from `const ValueType&` to `ValueType&&` in version
   3.11.0. Deleted overload for integral key types added in version 3.13.0 to reject such calls at compile time
   instead of causing undefined behavior at runtime.
-2. Added in version 3.11.0. Made `ValueType` the first template parameter in version 3.11.2. Support for keys
+2. Added in version 3.11.0. Made `ValueType` the first template parameter in version 3.11.2. Fixed in version 3.13.0
-   convertible to `std::string_view` added in version 3.13.0, consistently across the lookup functions.
+   to consistently accept `std::string_view`-convertible keys, as already supported by
-3. Added in version 2.0.2. Extended to work with arrays in version 3.13.0. Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109)
+   [`operator[]`](operator[].md), [`at`](at.md), [`find`](find.md), and other lookup functions.
 3. Added in version 2.0.2. Extended to work with arrays in version 3.13.0, including fixing an issue where resolving
   `ptr` through an array unexpectedly threw `out_of_range` instead of returning the resolved element (or
   `default_value`, as documented). Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109)
   instead of returning `default_value` for a one-character array index that is not a digit (e.g., `/x`) in version
   3.13.0, as it already did for longer ones.
@@ -9,8 +9,8 @@ class basic_json_document;
 A parsed JSON text, held as a flat index of its values
 ([16 bytes per value](../../home/architecture.md#node-index-of-json-views)) instead of a tree of `BasicJsonType` values.
-Strings and floating-point numbers stay in the source text; integers are converted while parsing, and strings that
+Strings and numbers stay in the source text; only strings that contain escapes are decoded, into one buffer owned by
-contain escapes are decoded into one buffer owned by the document. [`basic_json_view`](../basic_json_view/index.md) is a read-only handle to one value of a
+the document. [`basic_json_view`](../basic_json_view/index.md) is a read-only handle to one value of a
 `basic_json_document`; [`materialize()`](../basic_json_view/materialize.md) turns a subtree into the
 `BasicJsonType` value that [`BasicJsonType::parse()`](../basic_json/parse.md) would have produced for it.
@@ -115,13 +115,6 @@ points apply to every edit:
  [`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.
 ## See also
 - [Zero-copy JSON views](../../features/json_view.md) - guide to documents and views
 - [**basic_json_view**](../basic_json_view/index.md) - the non-owning handle to a value in a document
 - [**json_document**](../json_document.md) and [**json_editable_document**](../json_editable_document.md) - the default specializations
 - [**materialize**](../basic_json_view/materialize.md) - build a `basic_json` value from a view
 ## Version history
 - Added in version 3.13.0.
@@ -21,19 +21,17 @@ static basic_json_document parse(IteratorType first, IteratorType last,
 Both overloads accept the same JSON text as [`BasicJsonType::parse()`](../basic_json/parse.md), with the same
 `ignore_comments`/`ignore_trailing_commas` options, but build a [`basic_json_document`](index.md) (a flat index into
-the input) instead of a tree of `BasicJsonType` values. They accept every input `BasicJsonType::parse()` takes, and in
+the input) instead of a tree of `BasicJsonType` values. They take the same inputs as `BasicJsonType::parse()`. Byte
-addition a pointer to a null-terminated wide string (which `BasicJsonType::parse()` rejects). Contiguous inputs of
+inputs that stay alive can be borrowed; all others (streams, `#!cpp FILE*`, wide characters, non-contiguous
-single-byte characters that stay alive can be borrowed; all others (streams, `#!cpp FILE*`, wide characters, which
+iterators) are read into a copy that the document owns -- see the Notes. Use [`parse_copy()`](parse_copy.md) to get an
-must be converted to UTF-8, and non-contiguous iterators) are read into a copy that the document owns -- see the
+owned copy of a borrowable input as well.
 Notes. Use [`parse_copy()`](parse_copy.md) to get an owned copy of a borrowable input
 as well.
 ## Template parameters
 `InputType`
 :   A compatible input, for instance:
-    - a `#!cpp std::string`, a `#!cpp std::string_view` (C++17), or a C-style array of single-byte characters
+    - a `#!cpp std::string`, `#!cpp std::string_view`, or a C-style array of single-byte characters
    - a pointer to a null-terminated string of single-byte characters (`#!cpp char`, `#!cpp signed char`,
      `#!cpp unsigned char`, `#!cpp std::uint8_t`)
    - a container for which `#!cpp obj.data()` and `#!cpp obj.size()` give contiguous single-byte access, e.g.
@@ -49,10 +47,6 @@ as well.
    `#!cpp std::string::iterator`; the iterators of single-byte characters are borrowed or read like the byte inputs
    above, those of wide characters are converted to UTF-8
 Ill-formed UTF-16 and UTF-32 sequences are rejected: a lone surrogate, a high surrogate that is not followed by its low
 surrogate, and a code point above `U+10FFFF` all yield a
 [`parse_error.101`](../../home/exceptions.md#jsonexceptionparse_error101).
 ## Parameters
 `input` (in)
@@ -161,5 +155,3 @@ buffer of a given length, pass a pair of pointers: `#!cpp parse(ptr, ptr + len)`
 ## Version history
 - Added in version 3.13.0.
 - Ill-formed UTF-16 and UTF-32 input (a lone surrogate, a high surrogate that is not followed by its low surrogate, or
  a code point above `U+10FFFF`) is rejected with `parse_error.101`.
@@ -80,8 +80,7 @@ None of these exceptions carry a [`JSON_DIAGNOSTICS`](../macros/json_diagnostics
   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). Constant if no element of the array is an array
+   index (unlike `BasicJsonType`'s array, which is random-access).
   or object, since the elements are then adjacent in the index.
 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 (as 1.) or the index into the array (as 2.).
@@ -28,8 +28,7 @@ This exception does not carry a [`JSON_DIAGNOSTICS`](../macros/json_diagnostics.
 Linear in the size of the array or object: unlike [`front()`](front.md), which only ever looks at the first
 element, `back()` has to walk every element to find where they end, since elements are not a fixed size in the
-index. Constant if no element of the array is an array or object, since the elements are then adjacent
+index.
 in the index.
 ## Notes
@@ -143,13 +143,6 @@ still refers to it -- including ones taken before the change -- reads the new va
 - [**source_offset**](source_offset.md) - byte offset of this value in the document's source text
 ## See also
 - [Zero-copy JSON views](../../features/json_view.md) - guide to documents and views
 - [**basic_json_document**](../basic_json_document/index.md) - the document that owns the parsed data
 - [**json_view**](../json_view.md) and [**json_editable_view**](../json_editable_view.md) - the default specializations
 - [**materialize**](materialize.md) - build a `basic_json` value from a view
 ## Version history
 - Added in version 3.13.0.
@@ -86,8 +86,7 @@ None of these exceptions carry a [`JSON_DIAGNOSTICS`](../macros/json_diagnostics
   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). Constant if no element of the array is an array
+   index (unlike `BasicJsonType`'s array, which is random-access).
   or object, since the elements are then adjacent in the index.
 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 (as 1.) or the index into the array (as 2.).
@@ -51,4 +51,4 @@ byte_container_with_subtype(container_type&& container, subtype_type subtype);
 ## Version history
-Added in version 3.8.0.
+Since version 3.8.0.
@@ -39,4 +39,4 @@ Constant.
 ## Version history
-Added in version 3.8.0.
+Since version 3.8.0.
@@ -42,4 +42,4 @@ Constant.
 ## Version history
-Added in version 3.8.0.
+Since version 3.8.0.
@@ -29,14 +29,6 @@ specific naming scheme in order to override the binary type.
 - [**has_subtype**](has_subtype.md) - return whether the value has a subtype
 - [**clear_subtype**](clear_subtype.md) - clears the binary subtype
 ## See also
 - [Binary values](../../features/binary_values.md) - how binary values and subtypes are handled
 - [**binary**](../basic_json/binary.md) - create a binary array value
 - [**get_binary**](../basic_json/get_binary.md) - get a reference to the stored binary value
 - [**binary_t**](../basic_json/binary_t.md) - type for binary arrays
 - [Binary formats](../../features/binary_formats/index.md) - formats that can store binary values
 ## Version history
 - Added in version 3.8.0.
@@ -44,4 +44,4 @@ Constant.
 ## Version history
-Added in version 3.8.0.
+Since version 3.8.0.
@@ -30,4 +30,4 @@ types.
 ## Version history
-Added in version 1.0.0.
+Since version 1.0.0.
@@ -32,4 +32,4 @@ specialization.
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -40,4 +40,4 @@ parsing, without ever rewriting the source text -- see [Edits](basic_json_docume
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -38,4 +38,4 @@ still referring to it seeing the change, see [Edits](basic_json_document/index.m
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -51,5 +51,5 @@ operator string_t() const
 ## Version history
- Added in version 2.0.0.
+- Since version 2.0.0.
 - Changed type to `string_t` and deprecated in version 3.11.0.
@@ -12,8 +12,7 @@ Parent of this JSON pointer; in case this JSON pointer is the root, the root its
 ## Exception safety
-Strong exception safety: if an exception occurs, the original value stays intact. The function is not `#!cpp noexcept`
+No-throw guarantee: this function never throws exceptions.
 and allocates a new JSON pointer, so it can throw `#!cpp std::bad_alloc`; it throws no library exceptions.
 ## Complexity
@@ -49,5 +49,5 @@ ptr == json_pointer(ptr.to_string());
 ## Version history
- Added in version 2.0.0.
+- Since version 2.0.0.
 - Changed return type to `string_t` in version 3.11.0.
@@ -59,13 +59,6 @@ leading `-` sign.
 - [**start_object**](start_object.md) (_virtual_) - the beginning of an object was read
 - [**string**](string.md) (_virtual_) - a string value was read
 ## See also
 - [SAX interface](../../features/parsing/sax_interface.md) - guide to event-based parsing
 - [**sax_parse**](../basic_json/sax_parse.md) - generate SAX events from an input
 - [**parse**](../basic_json/parse.md) - DOM parsing, with optional [parser callbacks](../../features/parsing/parser_callbacks.md)
 - [Parse exceptions](../../features/parsing/parse_exceptions.md)
 ## Version history
 - Added in version 3.2.0.
@@ -31,4 +31,4 @@ This type is a [`basic_json_view`](basic_json_view/index.md) of a value of a [`j
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -138,12 +138,3 @@ header. See also the [macro overview page](../../features/macros.md).
  a derived class; uses default values; uses custom names
 - [**NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE_ONLY_SERIALIZE_WITH_NAMES**](nlohmann_define_type_with_names.md) - serialize a derived
  class; uses custom names
 ## See also
 - [Macros](../../features/macros.md) - guide to the supported macros
 - [Runtime assertions](../../features/assertions.md)
 - [Arbitrary type conversions](../../features/arbitrary_types.md) - using the `NLOHMANN_DEFINE_TYPE_*` macros
 - [Enum conversion](../../features/enum_conversion.md) - using `NLOHMANN_JSON_SERIALIZE_ENUM`
 - [The `nlohmann` namespace](../../features/namespace.md)
 - [CMake integration](../../integration/cmake.md) - setting macros from the build system
@@ -38,7 +38,7 @@ Therefore, assertions can be switched off by defining `NDEBUG`.
    ```cpp
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -64,7 +64,7 @@ Therefore, assertions can be switched off by defining `NDEBUG`.
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -79,7 +79,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    ```cpp
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -98,7 +98,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #define JSON_BRACE_INIT_COPY_SEMANTICS 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -54,7 +54,7 @@ The default value is `0` (disabled, the deprecated functions can still be called
    ```cpp
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -72,7 +72,7 @@ The default value is `0` (disabled, the deprecated functions can still be called
    #define JSON_DELETE_DEPRECATED_FUNCTIONS 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -39,7 +39,7 @@ The default value is `0`.
    #define JSON_DISABLE_ENUM_SERIALIZATION 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    enum class Choice
    {
@@ -66,7 +66,7 @@ The default value is `0`.
    #define JSON_DISABLE_ENUM_SERIALIZATION 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    enum class Choice
    {
@@ -99,7 +99,7 @@ The default value is `0`.
    #define JSON_DISABLE_ENUM_SERIALIZATION 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    enum class Choice
    {
@@ -92,7 +92,7 @@ The default value is `0`: streams are scanned in bulk.
    #include <sstream>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -115,7 +115,7 @@ The default value is `0`: streams are scanned in bulk.
    #include <sstream>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -72,7 +72,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    ```cpp
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -89,7 +89,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #define JSON_DISABLE_TUPLE_REFERENCE_CONVERSION 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -73,7 +73,7 @@ The default value is `0`: the file is locked once and read with the unlocked std
    #include <cstdio>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -92,7 +92,7 @@ The default value is `0`: the file is locked once and read with the unlocked std
    #include <cstdio>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -61,7 +61,7 @@ By default, `#!cpp JSON_NO_SIMD` is not defined, and vector instructions are use
    #include <iostream>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -94,7 +94,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #include <sstream>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -115,7 +115,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #include <sstream>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -64,7 +64,7 @@ The default value is `0` (disabled, the behavior of version 3.12.0 and earlier i
    ```cpp
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -81,7 +81,7 @@ The default value is `0` (disabled, the behavior of version 3.12.0 and earlier i
    #define JSON_STRICT_BINARY_UTF8 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -92,7 +92,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    ```cpp
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -109,7 +109,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #define JSON_STRICT_NUL_HANDLING 1
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    int main()
    {
@@ -77,7 +77,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #include <map>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    enum TaskState { TS_STOPPED, TS_RUNNING, TS_COMPLETED };
@@ -105,7 +105,7 @@ The default value is `0` (disabled — existing behavior is preserved).
    #include <map>
    #include <nlohmann/json.hpp>
-    using nlohmann::json;
+    using json = nlohmann::json;
    enum TaskState { TS_STOPPED, TS_RUNNING, TS_COMPLETED };
@@ -37,8 +37,7 @@ the stream `o`
 1. Throws [`type_error.316`](../home/exceptions.md#jsonexceptiontype_error316) if a string stored inside the JSON
   value is not UTF-8 encoded. Note that unlike the [`dump`](basic_json/dump.md) member functions, no `error_handler`
   can be set.
-2. Throws no library exceptions. As the string representation is built with [`to_string`](json_pointer/to_string.md),
+2. None.
   `#!cpp std::bad_alloc` is possible.
 ## Complexity
@@ -42,4 +42,4 @@ parsing an object of `n` keys costs O(n²) rather than O(n log n). See
 ## Version history
-Added in version 3.9.0.
+Since version 3.9.0.
@@ -35,4 +35,4 @@ of object keys, instead of sorting them like [`json_document`](json_document.md)
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -44,4 +44,4 @@ members [`set`](basic_json_document/set.md) added -- instead of sorting them lik
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -37,4 +37,4 @@ This type is a [`basic_json_view`](basic_json_view/index.md) of a value of an
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -32,4 +32,4 @@ This type is a [`basic_json_view`](basic_json_view/index.md) of a value of an
 ## Version history
-Added in version 3.13.0.
+Since version 3.13.0.
@@ -188,13 +188,10 @@ Note: Some modern features (like C++20 ranges or filesystem support) may be disa
        ```
 - [x] The code is checked with the latest [Cppcheck](https://cppcheck.sourceforge.io) with all warnings enabled.
- [x] The code is checked with the latest [Clang Static Analyzer](https://clang-analyzer.llvm.org) with 52 enabled
+- [x] The code is checked with the latest [Clang Static Analyzer](https://clang-analyzer.llvm.org) with 89 enabled
-  checkers.
+  rules.
 - [x] The code is checked with [Infer](https://fbinfer.com).
 - [x] The code is checked with [Codacy](https://app.codacy.com/gh/nlohmann/json/dashboard).
 - [x] The code is scanned with [CodeQL](https://codeql.github.com), [Semgrep](https://semgrep.dev), and
  [Flawfinder](https://dwheeler.com/flawfinder/) on every push and pull request and on a schedule; the findings are
  reported to GitHub's code scanning.
 ## Dynamic analysis
@@ -207,8 +204,6 @@ Note: Some modern features (like C++20 ranges or filesystem support) may be disa
 - [x] The test suite is executed with [Valgrind](https://valgrind.org) (Memcheck) to detect memory leaks.
 - [x] The test suite is executed with [Sanitizers](https://github.com/google/sanitizers) (address sanitizer, undefined
  behavior sanitizer, integer overflow detection, nullability violations).
 - [x] The fuzz targets are run with [CIFuzz](https://google.github.io/oss-fuzz/getting-started/continuous-integration/)
  on every pull request to catch regressions before they are merged.
 ## Dependencies
@@ -228,8 +223,6 @@ Note: Some modern features (like C++20 ranges or filesystem support) may be disa
  No release is made while such an alert is open.
 - [x] Third-party code included in the repository for testing, such as [doctest](https://github.com/doctest/doctest),
  is updated manually.
 - [x] The repository is evaluated with the [OpenSSF Scorecard](https://securityscorecards.dev) on a schedule and on
  every push to the default branch, and the results are reported to GitHub's code scanning.
 ## Style check
@@ -265,21 +258,4 @@ Note: Some modern features (like C++20 ranges or filesystem support) may be disa
 - [x] The library is tested against relevant CMake versions:
  - CMake 3.5 (the earliest supported)
  - CMake 3.31.6 (the latest 3.x release)
-  - CMake 4.0.0 (the first 4.x release)
+  - CMake 4.0.0 (a very recent release)
 !!! success "Requirement: Other build systems"
    The library can be used with build systems and package managers other than CMake.
 - [x] The library can be consumed with [Meson](https://json.nlohmann.me/integration/package_managers/) and the Swift
  Package Manager; the installation with Meson and the resolution of `Package.swift` are tested in the CI.
 !!! success "Requirement: Reproducible and verifiable builds"
    The library can be built and tested without network access or a Git checkout, and its licensing is machine-readable.
 - [x] The test suite is executed from an exported source tree without the `.git` directory and with the test data
  being available offline.
 - [x] The test suite is executed without the tests that change installed files to check that builds are reproducible.
 - [x] The repository is checked for compliance with the [REUSE specification](https://reuse.software) so that the
  license and copyright of every file is machine-readable.
 - [x] The documentation is built with warnings treated as errors, and its links are checked regularly.
@@ -58,7 +58,7 @@ particular, a 3.x release does not:
 - remove or rename a documented macro, CMake option, CMake target, or header, or change what a documented macro does.
 Exceptions to these rules, for instance when fixing a bug requires changing the exception a function throws, are
-documented in the [release notes](../home/releases/index.md).
+documented in the [release notes](../home/releases.md).
 The following are **not** part of the public API and may change in any release, including patch releases:
@@ -18,32 +18,3 @@
    white-space: nowrap;
    cursor: help;
 }
 /* byte layout tables of the binary formats */
 .md-typeset .byte-layout td code {
    white-space: pre-wrap;
 }
 .md-typeset .bl {
    display: inline-block;
    padding: 0 .25em;
    border-radius: .2em;
    font-family: var(--md-code-font-family);
    font-size: .85em;
    white-space: nowrap;
 }
 .md-typeset .bl-t {
    background-color: rgba(66, 133, 244, .25);
    box-shadow: inset 0 -.12em 0 rgba(66, 133, 244, .8);
 }
 .md-typeset .bl-l {
    background-color: rgba(251, 140, 0, .25);
    box-shadow: inset 0 -.12em 0 rgba(251, 140, 0, .8);
 }
 .md-typeset .bl-d {
    background-color: rgba(67, 160, 71, .25);
    box-shadow: inset 0 -.12em 0 rgba(67, 160, 71, .8);
 }
@@ -2,7 +2,7 @@
 #include <iomanip>
 #include <nlohmann/json.hpp>
-using nlohmann::json;
+using json = nlohmann::json;
 int main()
 {
@@ -2,7 +2,7 @@
 #include <vector>
 #include <nlohmann/json.hpp>
-using nlohmann::json;
+using json = nlohmann::json;
 int main()
 {
@@ -2,19 +2,19 @@
 #include <iomanip>
 #include <nlohmann/json.hpp>
-using nlohmann::json;
+using json = nlohmann::json;
 int main()
 {
    // a valid JSON text
-    const auto* valid_text = R"(
+    auto valid_text = R"(
    {
        "numbers": [1, 2, 3]
    }
    )";
    // an invalid JSON text
-    const auto* invalid_text = R"(
+    auto invalid_text = R"(
    {
        "strings": ["extra", "comma", ]
    }
@@ -1,18 +0,0 @@
 #include <iostream>
 #include <string>
 #include <nlohmann/json.hpp>
 using nlohmann::json;
 int main()
 {
    // a valid JSON text, given as UTF-16
    const std::u16string valid_text = u"{\"name\":\"\u00e9\"}";
    // an invalid JSON text, given as UTF-16
    const std::u16string invalid_text = u"{\"name\":\"\u00e9\",}";
    std::cout << std::boolalpha
              << json::accept(valid_text) << ' '
              << json::accept(invalid_text) << '\n';
 }
@@ -1 +0,0 @@
 true false
@@ -1,7 +1,7 @@
 #include <iostream>
 #include <nlohmann/json.hpp>
-using nlohmann::json;
+using json = nlohmann::json;
 int main()
 {
@@ -2,9 +2,9 @@
 #include <iomanip>
 #include <nlohmann/json.hpp>
-using nlohmann::json;
+using json = nlohmann::json;
 int main()
 {
-    std::cout << std::boolalpha << std::is_same<std::vector<json>, json::array_t>::value << '\n';
+    std::cout << std::boolalpha << std::is_same<std::vector<json>, json::array_t>::value << std::endl;
 }
`@@ -84,4 +84,4 @@ constructor.`

	`## Version history`	`## Version history`

	`- Added in version 3.0.0.`	`- Since version 3.0.0.`
`@@ -75,4 +75,4 @@ classDiagram`

	`## Version history`	`## Version history`

	`- Added in version 3.0.0.`	`- Since version 3.0.0.`
`@@ -51,4 +51,4 @@ deserializes. See [Template Parameter Requirements](../../features/types/templat`

	`## Version history`	`## Version history`

	`- Added in version 2.1.0.`	`- Since version 2.0.0.`
`@@ -76,4 +76,4 @@ classDiagram`

	`## Version history`	`## Version history`

	`- Added in version 3.0.0.`	`- Since version 3.0.0.`
`@@ -84,4 +84,4 @@ or the end of file. This also holds true when reading a byte vector for binary f`

	`## Version history`	`## Version history`

	`- Added in version 3.0.0.`	`- Since version 3.0.0.`
`@@ -51,4 +51,4 @@ byte_container_with_subtype(container_type&& container, subtype_type subtype);`

	`## Version history`	`## Version history`

	`Added in version 3.8.0.`	`Since version 3.8.0.`
`@@ -39,4 +39,4 @@ Constant.`

	`## Version history`	`## Version history`

	`Added in version 3.8.0.`	`Since version 3.8.0.`
`@@ -42,4 +42,4 @@ Constant.`

	`## Version history`	`## Version history`

	`Added in version 3.8.0.`	`Since version 3.8.0.`
`@@ -44,4 +44,4 @@ Constant.`

	`## Version history`	`## Version history`

	`Added in version 3.8.0.`	`Since version 3.8.0.`
`@@ -30,4 +30,4 @@ types.`

	`## Version history`	`## Version history`

	`Added in version 1.0.0.`	`Since version 1.0.0.`