Merge branch 'develop' into json-view/02b-float-parser

Conflicts: - number_parse.hpp: kept this branch's float parser, which replaces the Eisel-Lemire code that develop's side changed (#5750 made its digit counter unsigned; this parser has no such counter, and it compiles cleanly with GCC's -Wstrict-overflow=5). - number_handling.md, template_parameters.md: kept this branch's description of the conversion and added develop's "Before version 3.13.0" sentence. Ran make amalgamate. Signed-off-by: Niels Lohmann <mail@nlohmann.me>
Review and extend the documentation, and check it in CI (#5638 )
2026-10-02 20:50:32 +00:00 · 2026-10-02 11:35:40 +02:00 · 2026-10-02 11:32:15 +02:00 · 2026-10-02 11:24:33 +02:00 · 2026-10-02 11:23:55 +02:00 · 2026-10-02 07:47:50 +02:00
329 changed files with 8355 additions and 3904 deletions
@@ -84,6 +84,10 @@ Checks: '*,
 CheckOptions:
  - key: hicpp-special-member-functions.AllowSoleDefaultDtor
    value: 1
+  # clang-tidy 22.1 extended this check to classes and enums; the test files
+  # define many such helper types at namespace scope, which is harmless
+  - key: misc-use-internal-linkage.AnalyzeTypes
+    value: false

 WarningsAsErrors: '*'

@@ -142,6 +142,16 @@ The documentation will then be available at <http://127.0.0.1:8000/>. See the do
 [mkdocs](https://www.mkdocs.org) and [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/) for more
 information.

+Before opening a pull request, check the documentation like the CI does:
+
+```shell
+make build -C docs/mkdocs          # strict build: fails on broken links, anchors, and structure problems
+make check_mermaid -C docs/mkdocs  # checks the Mermaid diagrams (requires Node.js)
+```
+
+A new API page also needs an entry in [`docs/docset/docSet.sql`](https://github.com/nlohmann/json/blob/develop/docs/docset/docSet.sql),
+the search index of the docset; `make build` reports missing entries.
+
 ### Amalgamate the source code

 The single-header files
@@ -18,6 +18,17 @@ updates:
    cooldown:
      default-days: 7

+  - package-ecosystem: npm
+    directory: /docs/mkdocs/scripts/mermaid
+    schedule:
+      interval: daily
+    cooldown:
+      default-days: 7
+    ignore:
+      # Material for MkDocs loads mermaid@11; keep the checker on the same major version
+      - dependency-name: mermaid
+        update-types: ["version-update:semver-major"]
+
  - package-ecosystem: pip
    directory: /tools/astyle
    schedule:
@@ -0,0 +1,53 @@
+name: "Cancel runs of closed pull requests"
+
+# The concurrency groups of the other workflows cancel superseded runs when a
+# pull request gets new commits, but nothing stops the runs of its last commit
+# once the pull request is merged or closed. They then keep the runners busy
+# for hours while the queue of the open pull requests waits.
+#
+# pull_request_target is needed to get a token that can cancel runs for pull
+# requests from forks. This is safe because the workflow never checks out or
+# runs code from the pull request; it only calls the API.
+on:
+  pull_request_target:
+    types: [closed]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  cancel:
+    permissions:
+      actions: write
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Harden Runner
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
+        with:
+          egress-policy: audit
+
+      - name: Cancel unfinished runs of the pull request's head commit
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+          SELF: ${{ github.run_id }}
+        # only runs triggered by the pull request: when a branch is pushed to
+        # develop directly, its push runs share the head commit
+        run: |
+          gh api --paginate "repos/$GH_REPO/actions/runs?head_sha=$HEAD_SHA&per_page=100" \
+            --jq ".workflow_runs[]
+                  | select(.status != \"completed\" and .id != $SELF)
+                  | select(.event == \"pull_request\" or .event == \"pull_request_target\")
+                  | \"\(.id) \(.name)\"" |
+          while read -r id name; do
+            echo "Cancelling run $id ($name)"
+            # a run may finish between listing and cancelling; that is not an error
+            gh run cancel "$id" || true
+          done
@@ -2,16 +2,23 @@ name: "Check amalgamation"

 on:
  pull_request:
+  # also check develop itself: a PR can be merged before its own run of this
+  # workflow completes (e.g. while it is still queued), leaving single_include
+  # stale on develop without any failing check
+  push:
+    branches:
+      - develop

 concurrency:
  group: ${{ github.workflow }}-${{ github.ref || github.run_id }}
-  cancel-in-progress: true
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}

 permissions:
  contents: read

 jobs:
  save:
+    if: github.event_name == 'pull_request'
    runs-on: ubuntu-latest
    steps:
      - name: Harden Runner
@@ -43,11 +50,11 @@ jobs:
        with:
          egress-policy: audit

-      - name: Checkout pull request
+      - name: Checkout pull request or pushed commit
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
        with:
          path: main
-          ref: ${{ github.event.pull_request.head.sha }}
+          ref: ${{ github.event.pull_request.head.sha || github.sha }}
          persist-credentials: false

      - name: Checkout tools
@@ -0,0 +1,46 @@
+name: Check documentation links
+
+# check the links of the documentation weekly; external links break without any change in this repository
+on:
+  schedule:
+    - cron: '17 4 * * 1'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}
+  cancel-in-progress: true
+
+jobs:
+  check_docs_links:
+    if: github.repository == 'nlohmann/json'
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - name: Harden Runner
+        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
+        with:
+          egress-policy: audit
+
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+
+      - name: Install virtual environment
+        run: make install_venv -C docs/mkdocs
+
+      - name: Check links
+        shell: bash  # adds -o pipefail, so tee does not hide the exit code
+        run: make link_check -C docs/mkdocs 2>&1 | tee link_check.log
+
+      - name: Summarize broken links
+        if: failure()
+        run: |
+          {
+            echo '### Broken documentation links'
+            echo '```'
+            grep 'invalid url' link_check.log || true
+            echo '```'
+          } >> "$GITHUB_STEP_SUMMARY"
@@ -38,14 +38,14 @@ jobs:

    # Initializes the CodeQL tools for scanning.
    - name: Initialize CodeQL
-      uses: github/codeql-action/init@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+      uses: github/codeql-action/init@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2
      with:
        languages: c-cpp

    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
    # If this step fails, then you should remove it and run the build manually (see below)
    - name: Autobuild
-      uses: github/codeql-action/autobuild@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+      uses: github/codeql-action/autobuild@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2

    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+      uses: github/codeql-action/analyze@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2
@@ -10,7 +10,8 @@ permissions:

 jobs:
  comment:
-    if: ${{ github.event.workflow_run.conclusion == 'failure' }}
+    # push runs on develop have no PR to comment on (and no "pr" artifact)
+    if: ${{ github.event.workflow_run.conclusion == 'failure' && github.event.workflow_run.event == 'pull_request' }}
    runs-on: ubuntu-latest
    permissions:
      contents: read
@@ -47,6 +47,6 @@ jobs:
          output: 'flawfinder_results.sarif'

      - name: Upload analysis results to GitHub Security tab
-        uses: github/codeql-action/upload-sarif@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+        uses: github/codeql-action/upload-sarif@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2
        with:
          sarif_file: ${{github.workspace}}/flawfinder_results.sarif
@@ -43,6 +43,9 @@ jobs:
      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
        with:
          persist-credentials: false
+          # the git-revision-date-localized plugin needs the history for correct "last update" dates and so the
+          # strict build does not fail on a shallow clone
+          fetch-depth: 0

      - name: Install virtual environment
        run: make install_venv -C docs/mkdocs
@@ -80,6 +80,6 @@ jobs:

      # Upload the results to GitHub's code scanning dashboard.
      - name: "Upload to code-scanning"
-        uses: github/codeql-action/upload-sarif@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+        uses: github/codeql-action/upload-sarif@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2
        with:
          sarif_file: results.sarif
@@ -65,7 +65,7 @@ jobs:

      # Upload SARIF file generated in previous step
      - name: Upload SARIF file
-        uses: github/codeql-action/upload-sarif@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+        uses: github/codeql-action/upload-sarif@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 # v4.38.2
        with:
          sarif_file: semgrep.sarif
        if: always()
@@ -400,7 +400,7 @@ jobs:
    runs-on: ubuntu-latest
    strategy:
      matrix:
-        target: [ci_test_examples, ci_test_build_documentation]
+        target: [ci_test_examples, ci_test_build_documentation, ci_test_documentation_mermaid]
    steps:
      - name: Harden Runner
        uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
@@ -410,6 +410,12 @@ jobs:
      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
        with:
          persist-credentials: false
+          # the git-revision-date-localized plugin needs the history; a shallow clone makes the strict build fail
+          fetch-depth: ${{ matrix.target == 'ci_test_build_documentation' && '0' || '1' }}
+      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        if: matrix.target == 'ci_test_documentation_mermaid'
+        with:
+          node-version: 24
      - name: Run CMake
        run: cmake -S . -B build -DJSON_CI=On
      - name: Build
@@ -28,6 +28,8 @@
 /docs/docset/docSet.dsidx
 /docs/mkdocs/.cache/
 /docs/mkdocs/docs/__pycache__/
+/docs/mkdocs/hooks/__pycache__/
+/docs/mkdocs/scripts/mermaid/node_modules/
 /docs/mkdocs/site/
 /docs/mkdocs/venv/

@@ -61,7 +61,6 @@ option(JSON_Install                        "Install CMake targets during install
 option(JSON_MultipleHeaders                "Use non-amalgamated version of the library." ON)
 option(JSON_SystemInclude                  "Include as system headers (skip for clang-tidy)." OFF)
 option(JSON_StrictNulHandling              "Build with strict NUL-byte handling enabled." OFF)
-option(JSON_StrictBinaryUTF8               "Build with UTF-8 checks in the CBOR, UBJSON, BJData, and BSON writers enabled." OFF)

 if (JSON_CI)
    include(ci)
@@ -119,10 +118,6 @@ if (JSON_StrictNulHandling)
    message(STATUS "Strict NUL-byte handling enabled (JSON_STRICT_NUL_HANDLING=1)")
 endif()

-if (JSON_StrictBinaryUTF8)
-    message(STATUS "Strict UTF-8 checks in binary writers enabled (JSON_STRICT_BINARY_UTF8=1)")
-endif()
-
 if (JSON_Diagnostic_Positions)
    message(STATUS "Diagnostic positions enabled (JSON_DIAGNOSTIC_POSITIONS=1)")
 endif()
@@ -158,7 +153,6 @@ target_compile_definitions(
    $<$<BOOL:${JSON_Diagnostic_Positions}>:JSON_DIAGNOSTIC_POSITIONS=1>
    $<$<BOOL:${JSON_LegacyDiscardedValueComparison}>:JSON_USE_LEGACY_DISCARDED_VALUE_COMPARISON=1>
    $<$<BOOL:${JSON_StrictNulHandling}>:JSON_STRICT_NUL_HANDLING=1>
-    $<$<BOOL:${JSON_StrictBinaryUTF8}>:JSON_STRICT_BINARY_UTF8=1>
 )

 target_include_directories(
@@ -12,7 +12,6 @@
 [![Documentation](https://img.shields.io/badge/docs-mkdocs-blue.svg)](https://json.nlohmann.me)
 [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/nlohmann/json/develop/LICENSE.MIT)
 [![GitHub Releases](https://img.shields.io/github/release/nlohmann/json.svg)](https://github.com/nlohmann/json/releases)
-[![Packaging status](https://repology.org/badge/tiny-repos/nlohmann-json.svg)](https://repology.org/project/nlohmann-json/versions)
 [![GitHub Downloads](https://img.shields.io/github/downloads/nlohmann/json/total)](https://github.com/nlohmann/json/releases)
 [![GitHub Issues](https://img.shields.io/github/issues/nlohmann/json.svg)](https://github.com/nlohmann/json/issues)
 [![Average time to resolve an issue](https://isitmaintained.com/badge/resolution/nlohmann/json.svg)](https://isitmaintained.com/project/nlohmann/json "Average time to resolve an issue")
@@ -1394,7 +1393,7 @@ THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR I
 - The class contains a slightly modified version of the Grisu2 algorithm from Florian Loitsch which is licensed under the [MIT License](https://opensource.org/licenses/MIT) (see above). Copyright &copy; 2009 [Florian Loitsch](https://florian.loitsch.com/)
 - The class contains a copy of [Hedley](https://nemequ.github.io/hedley/) from Evan Nemerson which is licensed as [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
 - 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 and its table of powers of five 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 &copy; 2021 The fast_float authors
+- 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 &copy; 2021 The fast_float authors

 <img align="right" src="https://git.fsfe.org/reuse/reuse-ci/raw/branch/master/reuse-horizontal.png" alt="REUSE Software">

@@ -596,7 +596,12 @@ foreach(SRC_FILE ${SRC_FILES})
    add_executable(single_${RELATIVE_SRC_FILE} EXCLUDE_FROM_ALL ${PROJECT_BINARY_DIR}/src_single/${RELATIVE_SRC_FILE}.cpp)
    target_include_directories(single_${RELATIVE_SRC_FILE} PRIVATE ${PROJECT_SOURCE_DIR}/include)
    target_compile_features(single_${RELATIVE_SRC_FILE} PRIVATE cxx_std_11)
+    if(RELATIVE_SRC_FILE STREQUAL "json")
+        # see below: report json.hpp's diagnostics without --error, so they do not fail the build
+        set_property(TARGET single_${RELATIVE_SRC_FILE} PROPERTY CXX_INCLUDE_WHAT_YOU_USE ${IWYU_TOOL} -Xiwyu --max_line_length=300)
+    else()
        set_property(TARGET single_${RELATIVE_SRC_FILE} PROPERTY CXX_INCLUDE_WHAT_YOU_USE "${iwyu_path_and_options}")
+    endif()
    # remember binary for ci_single_binaries
    list(APPEND single_binaries single_${RELATIVE_SRC_FILE})
    # json.hpp pulls together the whole library behind heavily templated, SFINAE-based code, and
@@ -658,14 +663,19 @@ function(ci_get_cmake version var)
            OUTPUT ${${var}}
            COMMAND wget -nc https://github.com/Kitware/CMake/releases/download/v${version}/cmake-${version}-linux-x86_64.tar.gz
            COMMAND wget -nc https://github.com/Kitware/CMake/releases/download/v${version}/cmake-${version}-SHA-256.txt
-            # verify the archive against Kitware's published SHA-256 sums before unpacking it
-            COMMAND sh -c "grep ' cmake-${version}-linux-x86_64[.]tar[.]gz$' cmake-${version}-SHA-256.txt | sha256sum -c -"
-            COMMAND tar xfz cmake-${version}-linux-x86_64.tar.gz
-            COMMAND rm cmake-${version}-linux-x86_64.tar.gz cmake-${version}-SHA-256.txt
+            # verify the archive against Kitware's published SHA-256 sums before unpacking it; old
+            # releases list the archive as "Linux-x86_64", so match case-insensitively and rewrite
+            # the name to the lowercase one the download was saved under
+            COMMAND sh -c "grep -i ' cmake-${version}-linux-x86_64[.]tar[.]gz$' cmake-${version}-SHA-256.txt | tr L l | sha256sum -c -"
+            # unpack into cmake-${version} directly, as the archive's top-level directory is spelled
+            # "Linux" in old releases and "linux" in newer ones
            COMMAND ${CMAKE_COMMAND} -E rm -rf cmake-${version}
-            COMMAND ${CMAKE_COMMAND} -E rename cmake-${version}-linux-x86_64 cmake-${version}
+            COMMAND ${CMAKE_COMMAND} -E make_directory cmake-${version}
+            COMMAND tar xfz cmake-${version}-linux-x86_64.tar.gz -C cmake-${version} --strip-components=1
+            COMMAND rm cmake-${version}-linux-x86_64.tar.gz cmake-${version}-SHA-256.txt
            WORKING_DIRECTORY ${PROJECT_BINARY_DIR}
            COMMENT "Download prebuilt CMake ${version}"
+            VERBATIM
        )
    else()
        # no prebuilt archive for this platform (e.g. macOS or Linux aarch64): build from source
@@ -691,7 +701,7 @@ ci_get_cmake(4.0.0  CMAKE_4_0_0_BINARY)
 # the tests require CMake 3.13 or later, so they are excluded for CMake 3.5.0
 set(JSON_CMAKE_FLAGS_3_5_0 JSON_Diagnostics JSON_Diagnostic_Positions JSON_GlobalUDLs JSON_ImplicitConversions JSON_DisableEnumSerialization
    JSON_LegacyDiscardedValueComparison JSON_Install JSON_MultipleHeaders JSON_SystemInclude JSON_Valgrind
-    JSON_StrictNulHandling JSON_StrictBinaryUTF8)
+    JSON_StrictNulHandling)
 set(JSON_CMAKE_FLAGS_3_31_6 JSON_BuildTests ${JSON_CMAKE_FLAGS_3_5_0})
 set(JSON_CMAKE_FLAGS_4_0_0 JSON_BuildTests ${JSON_CMAKE_FLAGS_3_5_0})

@@ -891,6 +901,12 @@ add_custom_target(ci_test_build_documentation
    COMMENT "Build the documentation"
 )

+add_custom_target(ci_test_documentation_mermaid
+    COMMAND make check_mermaid
+    WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/docs/mkdocs
+    COMMENT "Check the Mermaid diagrams of the documentation"
+)
+
 ###############################################################################
 # Clean up all generated files.
 ###############################################################################
@@ -164,7 +164,6 @@ set(GCC_CXXFLAGS
    -Wenum-conversion
    -Wexceptions
    -Wexpansion-to-defined
-    -Wexperimental-fmv-target
    -Wexpose-global-module-tu-local
    -Wexternal-tu-local
    -Wextra
@@ -46,9 +46,10 @@ create_output: $(EXAMPLES:.cpp=.output)
 # check output of all stand-alone example files
 check_output: $(EXAMPLES:.cpp=.test)

-# check output of all stand-alone example files (exclude files with platform-dependent output.)
+# check output of all stand-alone example files (exclude files whose output depends on the platform by nature:
+# library and compiler information, container size limits, and hash values)
 # This target is used in the CI (ci_test_documentation).
-check_output_portable: $(filter-out mkdocs/docs/examples/meta.test mkdocs/docs/examples/max_size.test mkdocs/docs/examples/std_hash.test mkdocs/docs/examples/basic_json__CompatibleType.test,$(EXAMPLES:.cpp=.test))
+check_output_portable: $(filter-out mkdocs/docs/examples/meta.test mkdocs/docs/examples/max_size.test mkdocs/docs/examples/std_hash.test,$(EXAMPLES:.cpp=.test))

 clean:
 	rm -fr $(EXAMPLES:.cpp=)
@@ -10,9 +10,12 @@ INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype',
 INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::byte_container_with_subtype', 'Constructor', 'api/byte_container_with_subtype/byte_container_with_subtype/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::clear_subtype', 'Method', 'api/byte_container_with_subtype/clear_subtype/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::has_subtype', 'Method', 'api/byte_container_with_subtype/has_subtype/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::operator!=', 'Operator', 'api/byte_container_with_subtype/operator_ne/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::operator==', 'Operator', 'api/byte_container_with_subtype/operator_eq/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::set_subtype', 'Method', 'api/byte_container_with_subtype/set_subtype/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('byte_container_with_subtype::subtype', 'Method', 'api/byte_container_with_subtype/subtype/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('basic_json', 'Class', 'api/basic_json/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('format_as', 'Function', 'api/basic_json/format_as/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('basic_json::accept', 'Function', 'api/basic_json/accept/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('basic_json::array', 'Function', 'api/basic_json/array/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('basic_json::array_t', 'Type', 'api/basic_json/array_t/index.html');
@@ -132,15 +135,19 @@ INSERT INTO searchIndex(name, type, path) VALUES ('json', 'Class', 'api/json/ind
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer', 'Class', 'api/json_pointer/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::back', 'Method', 'api/json_pointer/back/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::empty', 'Method', 'api/json_pointer/empty/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::front', 'Method', 'api/json_pointer/front/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::json_pointer', 'Constructor', 'api/json_pointer/json_pointer/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::operator==', 'Operator', 'api/json_pointer/operator_eq/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::operator!=', 'Operator', 'api/json_pointer/operator_ne/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::operator/', 'Operator', 'api/json_pointer/operator_slash/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::operator/=', 'Operator', 'api/json_pointer/operator_slasheq/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::operator string_t', 'Operator', 'api/json_pointer/operator_string_t/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::operator<=>', 'Operator', 'api/json_pointer/operator_spaceship/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::parent_pointer', 'Method', 'api/json_pointer/parent_pointer/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::pop_back', 'Method', 'api/json_pointer/pop_back/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::pop_front', 'Method', 'api/json_pointer/pop_front/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::push_back', 'Method', 'api/json_pointer/push_back/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::push_front', 'Method', 'api/json_pointer/push_front/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::string_t', 'Type', 'api/json_pointer/string_t/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_pointer::to_string', 'Method', 'api/json_pointer/to_string/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('json_sax', 'Class', 'api/json_sax/index.html');
@@ -163,6 +170,7 @@ INSERT INTO searchIndex(name, type, path) VALUES ('operator<<', 'Operator', 'api
 INSERT INTO searchIndex(name, type, path) VALUES ('operator>>', 'Operator', 'api/operator_gtgt/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('ordered_json', 'Class', 'api/ordered_json/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('ordered_map', 'Class', 'api/ordered_map/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('std::formatter<basic_json>', 'Class', 'api/basic_json/std_formatter/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('std::hash<basic_json>', 'Class', 'api/basic_json/std_hash/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('std::swap<basic_json>', 'Function', 'api/basic_json/std_swap/index.html');

@@ -195,17 +203,20 @@ INSERT INTO searchIndex(name, type, path) VALUES ('nlohmann Namespace', 'Guide',
 INSERT INTO searchIndex(name, type, path) VALUES ('Types', 'Guide', 'features/types/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Types: Number Handling', 'Guide', 'features/types/number_handling/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Object Order', 'Guide', 'features/object_order/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('Performance', 'Guide', 'features/performance/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Parsing', 'Guide', 'features/parsing/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Parsing: JSON Lines', 'Guide', 'features/parsing/json_lines/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Parsing: Parser Callbacks', 'Guide', 'features/parsing/parser_callbacks/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Parsing: Parsing and Exceptions', 'Guide', 'features/parsing/parse_exceptions/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Parsing: SAX Interface', 'Guide', 'features/parsing/sax_interface/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('Parsing: Untrusted Input', 'Guide', 'features/parsing/untrusted_input/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Runtime Assertions', 'Guide', 'features/assertions/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Specializing enum conversion', 'Guide', 'features/enum_conversion/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Supported Macros', 'Guide', 'features/macros/index.html');

 -- Macros
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_ASSERT', 'Macro', 'api/macros/json_assert/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_BRACE_INIT_COPY_SEMANTICS', 'Macro', 'api/macros/json_brace_init_copy_semantics/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_CATCH_USER', 'Macro', 'api/macros/json_throw_user/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_DIAGNOSTICS', 'Macro', 'api/macros/json_diagnostics/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_DIAGNOSTIC_POSITIONS', 'Macro', 'api/macros/json_diagnostic_positions/index.html');
@@ -215,34 +226,59 @@ INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_CPP_11', 'Macro', 'a
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_CPP_14', 'Macro', 'api/macros/json_has_cpp_11/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_CPP_17', 'Macro', 'api/macros/json_has_cpp_11/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_CPP_20', 'Macro', 'api/macros/json_has_cpp_11/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_CPP_23', 'Macro', 'api/macros/json_has_cpp_11/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_CPP_26', 'Macro', 'api/macros/json_has_cpp_11/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_EXPERIMENTAL_FILESYSTEM', 'Macro', 'api/macros/json_has_filesystem/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_FILESYSTEM', 'Macro', 'api/macros/json_has_filesystem/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_RANGES', 'Macro', 'api/macros/json_has_ranges/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_STATIC_RTTI', 'Macro', 'api/macros/json_has_static_rtti/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_STD_FORMAT', 'Macro', 'api/macros/json_has_std_format/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_HAS_THREE_WAY_COMPARISON', 'Macro', 'api/macros/json_has_three_way_comparison/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_NOEXCEPTION', 'Macro', 'api/macros/json_noexception/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_NO_AUTOMATIC_UDLS', 'Macro', 'api/macros/json_no_automatic_udls/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_NO_IO', 'Macro', 'api/macros/json_no_io/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_NO_THREAD_LOCAL', 'Macro', 'api/macros/json_no_thread_local/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_PRECISE_STREAM_POSITION', 'Macro', 'api/macros/json_precise_stream_position/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_SKIP_LIBRARY_VERSION_CHECK', 'Macro', 'api/macros/json_skip_library_version_check/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_SKIP_UNSUPPORTED_COMPILER_CHECK', 'Macro', 'api/macros/json_skip_unsupported_compiler_check/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_STRICT_NUL_HANDLING', 'Macro', 'api/macros/json_strict_nul_handling/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_THROW_USER', 'Macro', 'api/macros/json_throw_user/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_TRY_USER', 'Macro', 'api/macros/json_throw_user/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_USE_GLOBAL_UDLS', 'Macro', 'api/macros/json_use_global_udls/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_USE_IMPLICIT_CONVERSIONS', 'Macro', 'api/macros/json_use_implicit_conversions/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('JSON_USE_LEGACY_DISCARDED_VALUE_COMPARISON', 'Macro', 'api/macros/json_use_legacy_discarded_value_comparison/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('JSON_USE_SIMDUTF', 'Macro', 'api/macros/json_use_simdutf/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('Macros', 'Macro', 'api/macros/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_INTRUSIVE', 'Macro', 'api/macros/nlohmann_define_derived_type/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_INTRUSIVE_ONLY_SERIALIZE', 'Macro', 'api/macros/nlohmann_define_derived_type/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_INTRUSIVE_ONLY_SERIALIZE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_INTRUSIVE_WITH_DEFAULT', 'Macro', 'api/macros/nlohmann_define_derived_type/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_INTRUSIVE_WITH_DEFAULT_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_INTRUSIVE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE', 'Macro', 'api/macros/nlohmann_define_derived_type/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE_ONLY_SERIALIZE', 'Macro', 'api/macros/nlohmann_define_derived_type/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE_ONLY_SERIALIZE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE_WITH_DEFAULT', 'Macro', 'api/macros/nlohmann_define_derived_type/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE_WITH_DEFAULT_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_DERIVED_TYPE_NON_INTRUSIVE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_INTRUSIVE', 'Macro', 'api/macros/nlohmann_define_type_intrusive/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_INTRUSIVE_ONLY_SERIALIZE', 'Macro', 'api/macros/nlohmann_define_type_intrusive/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_INTRUSIVE_ONLY_SERIALIZE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_INTRUSIVE_WITH_DEFAULT', 'Macro', 'api/macros/nlohmann_define_type_intrusive/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_INTRUSIVE_WITH_DEFAULT_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_INTRUSIVE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE', 'Macro', 'api/macros/nlohmann_define_type_non_intrusive/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_ONLY_SERIALIZE', 'Macro', 'api/macros/nlohmann_define_type_non_intrusive/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_ONLY_SERIALIZE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_WITH_DEFAULT', 'Macro', 'api/macros/nlohmann_define_type_non_intrusive/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_WITH_DEFAULT_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE_WITH_NAMES', 'Macro', 'api/macros/nlohmann_define_type_with_names/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_NAMESPACE', 'Macro', 'api/macros/nlohmann_json_namespace/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_NAMESPACE_BEGIN', 'Macro', 'api/macros/nlohmann_json_namespace_begin/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_NAMESPACE_END', 'Macro', 'api/macros/nlohmann_json_namespace_begin/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_NAMESPACE_NO_VERSION', 'Macro', 'api/macros/nlohmann_json_namespace_no_version/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_SERIALIZE_ENUM', 'Macro', 'api/macros/nlohmann_json_serialize_enum/index.html');
+INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_SERIALIZE_ENUM_STRICT', 'Macro', 'api/macros/nlohmann_json_serialize_enum_strict/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_VERSION_MAJOR', 'Macro', 'api/macros/nlohmann_json_version_major/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_VERSION_MINOR', 'Macro', 'api/macros/nlohmann_json_version_major/index.html');
 INSERT INTO searchIndex(name, type, path) VALUES ('NLOHMANN_JSON_VERSION_PATCH', 'Macro', 'api/macros/nlohmann_json_version_major/index.html');
@@ -1,3 +1,8 @@
+# The MkDocs 2.0 banners of Material for MkDocs and ProperDocs (via mkdocs-redirects) are printed to stderr, not
+# logged, so they do not affect --strict; silence them anyway.
+export NO_MKDOCS_2_WARNING := true
+export DISABLE_MKDOCS_2_WARNING := true
+
 # serve the site locally
 serve: style_check
 	venv/bin/mkdocs serve
@@ -8,11 +13,17 @@ serve_dirty: style_check
 # This target is used in the CI (ci_test_build_documentation).
 # This target is used by the docset Makefile.
 build: style_check
-	venv/bin/mkdocs build
+	venv/bin/mkdocs build --strict

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

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

 ## Examples

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

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

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

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

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

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

 ## Notes

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

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

-#### Limits
+### Limits

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

-#### Storage
+### Storage

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

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

 - Added in version 1.0.0.
@@ -92,6 +92,20 @@ Strong exception safety: if an exception occurs, the original value stays intact
 3. Logarithmic in the size of the container.
 4. Logarithmic in the size of the container.

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

 ??? example "Example: (1) access specified array element with bounds checking"
@@ -99,6 +99,25 @@ basic_json(basic_json&& other) noexcept;
      elements of the pairs are treated as keys and the second elements are as values.
    3. In all other cases, an array is created.
    
+    The following flowchart also takes into account what happens when `type_deduction` is `#!cpp false`, in which case
+    `manual_type` decides between object and array, and an object can only be forced if `init` actually matches rule 2
+    (or is empty):
+
+    ```mermaid
+    flowchart TD
+        A(["initializer_list init"]) --> B{"empty, or every element is a 2-element<br/>array whose first element is a string?"}
+        B -->|"yes"| C{"type_deduction"}
+        B -->|"no"| D{"type_deduction"}
+        C -->|"true"| OBJ["create object"]
+        C -->|"false"| E{"manual_type"}
+        E -->|"object"| OBJ
+        E -->|"array"| ARR["create array"]
+        D -->|"true"| ARR
+        D -->|"false"| F{"manual_type"}
+        F -->|"array"| ARR
+        F -->|"object"| ERR["throw type_error.301"]
+    ```
+
    The rules aim to create the best fit between a C++ initializer list and JSON values. The rationale is as follows:
    
    1. The empty initializer list is written as `#!cpp {}` which is exactly an empty JSON object.
@@ -171,8 +190,8 @@ basic_json(basic_json&& other) noexcept;
    - `BasicJsonType` has different template arguments than `basic_json_t`.
    
    **Note:** For cross-`basic_json` conversions to produce correct results, the target `basic_json`'s
-    `object_t::key_type` and `string_t` must be directly constructible from the source `basic_json`'s
-    corresponding types. See the description of overload (4) above for details on what happens when
+    [`object_t`](object_t.md)`::key_type` and [`string_t`](string_t.md) must be directly constructible from the source
+    `basic_json`'s corresponding types. See the description of overload (4) above for details on what happens when
    this requirement is not met.

 `U`:
@@ -347,6 +366,22 @@ basic_json(basic_json&& other) noexcept;

    Note the output is platform-dependent.

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

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

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

 1. Since version 1.0.0.
@@ -37,6 +37,14 @@ Constant.
    --8<-- "examples/begin.output"
    ```

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

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

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

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

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

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

 ## Notes

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

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

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

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

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

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

-#### Storage
+### Storage

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

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

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

 ## Notes

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

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

-#### Storage
+### Storage

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

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

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

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

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

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

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

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

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

 - Added in version 1.0.0.
@@ -52,6 +52,11 @@ All iterators, pointers, and references related to this container are invalidate
    --8<-- "examples/clear.output"
    ```

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

 - Added in version 1.0.0.
@@ -67,6 +67,18 @@ Logarithmic in the size of the JSON object.

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

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

 ??? example "Example: (1) check with key"
@@ -36,6 +36,13 @@ Constant.
    --8<-- "examples/crbegin.output"
    ```

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

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

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

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

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

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

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

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

 ## Exception safety

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

 ## Exceptions

@@ -28,6 +28,11 @@ iterator is invalidated.

 reference to the inserted element

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

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

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

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

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

 - Added in version 1.0.0.
@@ -4,31 +4,15 @@
 enum class error_handler_t {
    strict,
    replace,
-    ignore,
-    keep
+    ignore
 };
 ```

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

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

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

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

 ??? example
@@ -59,8 +37,11 @@ keep
    --8<-- "examples/error_handler_t.output"
    ```

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

 - Added in version 3.4.0.
- Added `keep`, and made this enumeration apply to the binary readers and writers in addition to `dump`, in version
-  3.13.0.
@@ -27,7 +27,7 @@ Empty objects and arrays are flattened to `#!json null` and will not be reconstr

 ## Examples

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

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

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

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

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

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

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

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

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

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

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

 ## Complexity

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

 !!! warning "Deprecation"

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

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

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

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

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

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

 ## Complexity

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

 !!! warning "Deprecation"

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

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

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

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

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

 ## Complexity

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

 !!! warning "Deprecation"

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

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

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

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

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

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

 !!! warning "Deprecation"

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

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

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

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

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

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

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

 ## Examples

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

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

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

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

 associated allocator

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

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

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

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

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

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

 the input parameter, allowing chaining calls

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

 Depends on what `json_serializer<ValueType>` `from_json()` method throws
@@ -49,7 +54,7 @@ Depends on the `json_serializer<ValueType>::from_json()` implementation.
    The example below shows several conversions from JSON values to other types. There a few things to note: (1)
    Floating-point numbers can be converted to integers, (2) A JSON array can be converted to a standard
    `#!cpp std::vector<short>`, (3) A JSON object can be converted to C++ associative containers such as
-    `#cpp std::unordered_map<std::string, json>`.
+    `#!cpp std::map<std::string, json>`.
        
    ```cpp
    --8<-- "examples/get_to.cpp"
@@ -51,6 +51,11 @@ bon8
    --8<-- "examples/sax_parse__binary.output"
    ```

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

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

 ## Examples

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

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

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

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

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

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

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

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

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

    The example shows how `insert()` is used.
    
@@ -34,6 +34,13 @@ Constant.
    --8<-- "examples/is_array.output"
    ```

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

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

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

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

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

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

 ## Examples

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

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

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

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

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

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

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

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

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

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

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

 ## Notes

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

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

-#### Limitations
+### Limitations

 The type `CustomBaseClass` has to be a default-constructible, non-`final` class.
 `basic_json` only supports copy/move construction/assignment if `CustomBaseClass` does so as well.
@@ -43,6 +43,10 @@ A `CustomBaseClass` with non-static data members forfeits `basic_json`'s
    --8<-- "examples/json_base_class_t.output"
    ```

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

 - Added in version 3.12.0.
@@ -15,11 +15,11 @@ using json_serializer = JSONSerializer<T, SFINAE>;

 ## Notes

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

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

-#### Requirements
+### Requirements

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

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

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

    Note the output is platform-dependent.

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

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

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

 Linear in the lengths of `apply_patch`.
@@ -23,27 +23,28 @@ type to use.
 ## Template parameters

 `NumberFloatType`
-:   the type to store floating-point numbers. Parsing and serialization are implemented in terms of
-    `#!cpp std::strtof`/`#!cpp std::strtod`/`#!cpp std::strtold` and `#!cpp std::snprintf`, so the type must be
-    `#!cpp float`, `#!cpp double`, or `#!cpp long double`. The
+:   the type to store floating-point numbers. The parser converts `#!cpp float`, `#!cpp double`, and a
+    `#!cpp long double` that is IEEE 754 binary64 itself and other `#!cpp long double` formats with
+    `#!cpp std::from_chars` or `#!cpp std::strtold`, and serialization falls back to `#!cpp std::snprintf`, so the
+    type must be `#!cpp float`, `#!cpp double`, or `#!cpp long double`. The
    [binary formats](../../features/binary_formats/index.md) additionally require `#!cpp float` or `#!cpp double`,
    because they have no encoding for `#!cpp long double`. See
    [Template Parameter Requirements](../../features/types/template_parameters.md#numberfloattype).

 ## Notes

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

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

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

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

-#### Limits
+### Limits

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

-#### Storage
+### Storage

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

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

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

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

 ## Notes

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

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

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

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

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the range and precision of numbers.
@@ -57,7 +57,7 @@ will automatically be stored as [`number_unsigned_t`](number_unsigned_t.md) or [
 As this range is a subrange of the exactly supported range [INT64_MIN, INT64_MAX], this class's integer type is
 interoperable.

-#### Storage
+### Storage

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

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

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

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

 ## Notes

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

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

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

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

-#### Limits
+### Limits

 [RFC 8259](https://tools.ietf.org/html/rfc8259) specifies:
 > An implementation may set limits on the range and precision of numbers.
@@ -58,7 +58,7 @@ as [`number_integer_t`](number_integer_t.md) or [`number_float_t`](number_float_
 As this range is a subrange (when considered in conjunction with the `number_integer_t` type) of the exactly supported
 range [0, UINT64_MAX], this class's integer type is interoperable.

-#### Storage
+### Storage

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

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

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

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

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

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

 ## Notes

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

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

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

-#### Behavior
+### Behavior

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

-#### Limits
+### Limits

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

-#### Storage
+### Storage

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

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

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

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

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

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

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

 `#!cpp *this`

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

 1. Throws [`type_error.308`](../../home/exceptions.md#jsonexceptiontype_error308) when called on a type other than
@@ -136,6 +136,18 @@ Strong exception safety: if an exception occurs, the original value stays intact
        while `/foo/one/one/one` creates nested objects. This is not specified by the JSON Pointer RFC; it is
        this library's own, intentional disambiguation rule. See also [JSON Pointer](../../features/json_pointer.md).

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

 ??? example "Example: (1) access specified array element"
@@ -17,6 +17,11 @@ Implicit type conversion between the JSON value and a compatible value. The call

 copy of the JSON value, converted to `ValueType`

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

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

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

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

 ## Examples

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

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

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

    The example demonstrates comparing several JSON types against the null pointer (JSON `#!json null`).
        
@@ -60,6 +60,16 @@ Linear.
    Since C++20 overload resolution will consider the _rewritten candidate_ generated from
    [`operator<=>`](operator_spaceship.md).

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

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

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

 ??? example
@@ -9,17 +9,9 @@ bool operator!=(const_reference lhs, const ScalarType rhs) noexcept;  // (2)

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

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

 2. Compares a JSON value and a scalar or a scalar and a JSON value for inequality by converting the scalar to a JSON
@@ -52,6 +44,11 @@ Linear.

 ## Notes

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

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

 ## Examples

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

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

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

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

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

-1. Added in version 1.0.0. Added C++20 member functions in version 3.11.0. Changed in version 3.13.0 to remove 
-   special-casing for `NaN` and `discarded` values; `operator!=` now consistently means `!(a == b)`.
-2. Added in version 1.0.0. Added C++20 member functions in version 3.11.0. Changed in version 3.13.0 to remove
-   special-casing for `NaN` and `discarded` values; `operator!=` now consistently means `!(a == b)`.
+1. Added in version 1.0.0. Added a C++20 member function in version 3.11.0. Changed in version 3.13.0 to remove
+   special-casing for `NaN` and `discarded` values; `operator!=` now consistently means `!(a == b)`. Removed the C++20
+   member function in version 3.13.0; since C++20, the compiler rewrites `a != b` using `operator==`.
+2. Added in version 1.0.0. Changed in version 3.13.0 to remove special-casing for `NaN` and `discarded` values;
+   `operator!=` now consistently means `!(a == b)`. Since C++20, the compiler rewrites `a != b` using `operator==`.
@@ -47,6 +47,11 @@ Constant.
    --8<-- "examples/operator__value_t.output"
    ```

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

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

 ## Examples

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    You should be warned by your compiler with a `-Wdeprecated-declarations` warning if you are using a deprecated
    function.
+
+    See the [migration guide](../../integration/migration_guide.md#parsing) for how to update existing code.
@@ -24,6 +24,21 @@ The parser callback distinguishes the following events:

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

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

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

 ## Examples

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

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

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

    The example below shows where discarded values are removed. The array and the number are discarded in different
    ways, but in each case the parse result contains neither the value nor its key.
@@ -26,10 +26,24 @@ Strong guarantee: if an exception is thrown, there are no changes in the JSON va
 - Throws [`parse_error.104`](../../home/exceptions.md#jsonexceptionparse_error104) if the JSON patch does not consist of
  an array of objects.
 - Throws [`parse_error.105`](../../home/exceptions.md#jsonexceptionparse_error105) if the JSON patch is malformed (e.g.,
-  mandatory attributes are missing); example: `"operation add must have member path"`.
+  mandatory attributes are missing); example: `"operation 'add' must have member 'path'"`.
 - Throws [`out_of_range.401`](../../home/exceptions.md#jsonexceptionout_of_range401) if an array index is out of range.
+- Throws [`parse_error.106`](../../home/exceptions.md#jsonexceptionparse_error106) if an array index in a "path" or
+  "from" member begins with '0'; example: `"array index '01' must not begin with '0'"`.
+- Throws [`parse_error.107`](../../home/exceptions.md#jsonexceptionparse_error107) if a "path" or "from" member is not
+  empty and does not begin with a slash (`/`); example: `"JSON pointer must be empty or begin with '/' - was: 'a'"`.
+- Throws [`parse_error.108`](../../home/exceptions.md#jsonexceptionparse_error108) if a tilde (`~`) in a "path" or
+  "from" member is not followed by `0` or `1`; example: `"escape character '~' must be followed with '0' or '1'"`.
+- Throws [`parse_error.109`](../../home/exceptions.md#jsonexceptionparse_error109) if an array index in a "path" or
+  "from" member is not a number; example: `"array index 'foo' is not a number"`.
+- Throws [`out_of_range.402`](../../home/exceptions.md#jsonexceptionout_of_range402) if the array index `-` is used
+  where an existing element is required (the "path" of "replace", the "from" of "move" and "copy"); example:
+  `"array index '-' (3) is out of range"`.
 - Throws [`out_of_range.403`](../../home/exceptions.md#jsonexceptionout_of_range403) if a JSON pointer inside the patch
  could not be resolved successfully in the current JSON value; example: `"key baz not found"`.
+- Throws [`out_of_range.404`](../../home/exceptions.md#jsonexceptionout_of_range404) if a reference token of a JSON
+  pointer inside the patch cannot be resolved, e.g., `-` in a "remove" operation or `1a` for an array; example:
+  `"unresolved reference token '-'"`.
 - Throws [`out_of_range.405`](../../home/exceptions.md#jsonexceptionout_of_range405) if JSON pointer has no parent
  ("add", "remove", "move")
 - Throws [`out_of_range.411`](../../home/exceptions.md#jsonexceptionout_of_range411) if an "add" operation's target
@@ -53,7 +67,7 @@ is thrown. In any case, the original value is not changed: the patch is applied

 ## Examples

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

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

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

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

 ## Examples

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

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

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

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

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

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

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

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

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

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

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

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

    Note the output is platform-dependent.

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

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

 ## Notes

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

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

-#### Encoding
+### Encoding

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

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

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

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

-#### Storage
+### Storage

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

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

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

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

 - Added in version 1.0.0.
@@ -73,6 +73,16 @@ void swap(typename binary_t::container_type& other);
 `right` (in, out)
 :   value to exchange the contents with

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

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

 ## Examples

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

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

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

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

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

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

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

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

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

    The example below shows how binary values can be swapped with `swap()`.
    
@@ -5,18 +5,15 @@
 static std::vector<std::uint8_t> to_bjdata(const basic_json& j,
                                           const bool use_size = false,
                                           const bool use_type = false,
-                                           const bjdata_version_t version = bjdata_version_t::draft2,
-                                           const error_handler_t error_handler = error_handler_t::keep);
+                                           const bjdata_version_t version = bjdata_version_t::draft2);

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

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

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

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

 - Throws [`other_error.502`](../../home/exceptions.md#jsonexceptionother_error502) if `use_type` is true and `use_size`
-  is false.
- 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)
+  is false, and `j` contains a non-empty array, object, or binary value.

 ## Complexity

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

 ## Examples

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

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

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

 - [from_bjdata](from_bjdata.md) create a JSON value from an input in BJData format
@@ -102,6 +105,3 @@ Linear in the size of the JSON value `j`.

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

 ## Examples

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

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

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

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

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

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

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

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

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

 ## Complexity

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

 ## Examples

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

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

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

 - [from_bson](from_bson.md) create a JSON value from an input in BSON format
@@ -92,9 +95,6 @@ pass before anything is written.
 ## Version history

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 ## Complexity

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

 ## Examples

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

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

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

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

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

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

 ## Return value

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

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

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

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

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

 - Throws [`other_error.502`](../../home/exceptions.md#jsonexceptionother_error502) if `use_type` is true and `use_size`
-  is false.
- 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)
+  is false, and `j` contains a non-empty array, object, or binary value.

 ## Complexity

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

 ## Examples

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

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

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

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

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

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

 - Added in version 1.0.0.
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Niels Lohmann	83302ff69d	Merge branch 'develop' into json-view/02b-float-parser Conflicts: - number_parse.hpp: kept this branch's float parser, which replaces the Eisel-Lemire code that develop's side changed (#5750 made its digit counter unsigned; this parser has no such counter, and it compiles cleanly with GCC's -Wstrict-overflow=5). - number_handling.md, template_parameters.md: kept this branch's description of the conversion and added develop's "Before version 3.13.0" sentence. Ran make amalgamate. Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-02 11:35:40 +02:00
Niels Lohmann	63c10a51fc	Review and extend the documentation, and check it in CI (#5638 ) * Review and extend the documentation, and check it in CI A review of all documentation pages found factual errors, dead links, missing cross-references, and gaps in examples. This fixes them and adds checks so the same problems are caught automatically. Fixes: - wrong signatures and version histories (operator!= C++20 member, binary() subtype type, get<PointerType>(), JSON_NO_THREAD_LOCAL, ...) - stale descriptions (number parsing since #5283, UBJSON table, SAX example that no longer compiled, tsl::ordered_map advice) - dead internal and external links; repology.org badges (the domain is suspended) replaced by badges that query the registries directly - deprecation notes link the migration guide; the guide itself fixed Additions: - "See also" sections, cross-references, 25 runnable examples, 12 Mermaid diagrams, new API pages for json_pointer::operator<=> and byte_container_with_subtype::operator==/!= - landing page, guides for untrusted input and performance - "unreleased" badge after versions newer than the latest release Checks: - strict documentation build (broken links/anchors fail it); CI and the publish workflow fetch the full history the build needs - weekly external link check, Mermaid syntax check in CI - check_structure.py: example titles, heading levels, alt texts, header links, docset index coverage; its unused-example check works again - all examples produce the same output on every platform Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Keep the customer links that could not be fixed A dead link on the customers page is still the evidence of where the use of the library was documented. Keep the original URLs of the entries without a working replacement (Marne, Cisco Webex Desk Camera, Philips Hue, CyberArk) and exclude exactly these URLs from the link check. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Correct the duplicate-key recipe's claim about SAX positions The SAX interface's key() receives no position either; only parse_error() does. Also note that the recipe does not report the path to the repeated key (see discussion #5085). Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Say the library is available as a single header and mention json_fwd.hpp Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Correct documentation errors found while hunting for bugs - patch/patch_inplace: list the JSON pointer errors parse_error.106-109 and out_of_range.402/404, and quote the actual parse_error.105 message. - unflatten: list parse_error.106/107/108 and out_of_range.404. - to_bson: list out_of_range.415 (binary subtype above 255) and note that 412 and 415 are new in 3.13.0. - to_string: state that string_t must be convertible to std::string, also in the StringType requirements table. - JSON Lines: a `while (input >> j)` loop also throws after the last value for concatenated JSON values; show a loop that works for both. - BON8: a string gets 0xFF only if nothing follows it in the message; a string at the end of an array or object is ended by 0xFE. - custom_string_type.hpp: add operator+=(char), which the "Always required" list asks for (json_pointer::to_string, flatten, unflatten, and diff did not compile), and an ADL int_to_string for diff and items. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Cache the release headers with functools.lru_cache Codacy (Pylint) flagged the mutable default argument that header() used as its cache. functools.lru_cache keeps the same memoization without it. The script's output is unchanged. Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-02 11:32:15 +02:00
dependabot[bot]	48ff79647f	Bump the codeql-action group with 4 updates (#5743 ) Bumps the codeql-action group with 4 updates: [github/codeql-action/init](https://github.com/github/codeql-action), [github/codeql-action/autobuild](https://github.com/github/codeql-action), [github/codeql-action/analyze](https://github.com/github/codeql-action) and [github/codeql-action/upload-sarif](https://github.com/github/codeql-action). Updates `github/codeql-action/init` from 4.38.1 to 4.38.2 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/1c5b675653bb5c22dbe9b12b556ec555138e09fd...2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2) Updates `github/codeql-action/autobuild` from 4.38.1 to 4.38.2 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/1c5b675653bb5c22dbe9b12b556ec555138e09fd...2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2) Updates `github/codeql-action/analyze` from 4.38.1 to 4.38.2 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/1c5b675653bb5c22dbe9b12b556ec555138e09fd...2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2) Updates `github/codeql-action/upload-sarif` from 4.38.1 to 4.38.2 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/1c5b675653bb5c22dbe9b12b556ec555138e09fd...2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2) --- updated-dependencies: - dependency-name: github/codeql-action/init dependency-version: 4.38.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: codeql-action - dependency-name: github/codeql-action/autobuild dependency-version: 4.38.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: codeql-action - dependency-name: github/codeql-action/analyze dependency-version: 4.38.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: codeql-action - dependency-name: github/codeql-action/upload-sarif dependency-version: 4.38.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: codeql-action ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-10-02 11:24:33 +02:00
Niels Lohmann	4d46bce4e1	Fix CI on develop (#5750 ) * Fix CI configuration broken by recent merges and tool updates - gcc_flags.cmake: drop -Wexperimental-fmv-target, which GCC 16 accepts only on aarch64; amd64 rejects it, so every GCC job failed while checking the compiler. - ci_get_cmake: add VERBATIM so the checksum pipeline is passed to the shell intact (the unescaped `$'` broke the generated Makefile and build.ninja, failing ci_cmake_flags and ci_module_cpp20); match the SHA-256 entry case-insensitively, as CMake 3.5.0 lists the archive as "Linux-x86_64"; and unpack with --strip-components, as that archive's top-level directory is spelled "Linux" too. - ci_single_binaries: compile json.hpp's TU without IWYU's --error, as the comment above the gate already intends. - tests: restore -Wno-deprecated-declarations for all non-MSVC compilers (#5737 kept it for GCC only), as several tests call deprecated functions on purpose; include thirdparty/fifo_map as SYSTEM. - .clang-tidy: set misc-use-internal-linkage.AnalyzeTypes to false; clang-tidy 22.1 extended the check to classes and enums and flagged 100 test helper types. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Fix library warnings and a JSON_DIAGNOSTICS parent bug - binary_reader: pass integers to sax->number_integer() through conditional_static_cast<number_integer_t>, making the existing narrowing for a narrow number_integer_t explicit (MSVC C4244 and GCC -Wconversion/-Warith-conversion with the int16_t test from #5694); mark two Infer DEAD_STORE false positives with @infer-ignore. - to_json: set the parents of an array built from a C++20 range view after all elements are in place; a reallocating push_back moved the earlier elements and left their parent pointers stale, failing the JSON_DIAGNOSTICS invariant assertion. - json.hpp: suppress MSVC C4127 for the new is_ordered_map check in diff(), like the three existing ones; spell out std::formatter::parse's return and iterator types for clang-tidy 22.1. - number_parse: make the Eisel-Lemire digit counter unsigned (GCC -Wstrict-overflow). - string_utils: take encode_utf8's callable by const reference (cppcoreguidelines-missing-std-forward) and drop a \u from its doc comment (-Wdocumentation-unknown-command). - ordered_map: include <memory> for std::allocator (cpplint). Ran make amalgamate. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Fix tests failing in CI on develop - unit-allocator: skip the #5640 test under MSVC STL iterator debugging, where containers allocate a debug proxy in noexcept move constructors and a failing allocation terminates; move a decrement out of an if condition (bugprone-inc-dec-in-conditions). - unit-conversions: expect the "(/0)" path with JSON_DIAGNOSTICS; compare strict enums via get<>() rather than through the noexcept operator==(ScalarType, json), which bugprone-exception-escape flags. - unit-alt-string: suppress -Wexit-time-destructors for the strict enum macro and misc-use-internal-linkage for its enum. - unit-bjdata: call the static lookup functions through the type and pass unsigned char (-Wsign-conversion on amd64). - Mark Infer false positives with @infer-ignore in unit-diagnostics, unit-pointer_access, unit-udt, and unit-conversions. - Smaller clang-tidy 22.1 findings in unit-class_parser, unit-constructor2, unit-custom-base-class, unit-locale-cpp, and unit-noexcept. Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-02 11:23:55 +02:00
Niels Lohmann	6aec1a085f	Report BON8 input that ends after a UTF-8 lead byte as truncated (#5677 ) A lead byte (0xC2..0xF7) inside a string begins either another character (if a continuation byte follows) or an integer (otherwise). When the input ended right after the lead byte, the reader took the missing byte as "not a continuation byte", ended the string before the lead byte, and treated the lead byte as the start of the next value. With strict=false, a message cut off there was therefore read as a shorter value: the 11 bytes of "😀😀é" cut after 9 bytes gave "😀😀", and ["aé"] cut after 3 of its 5 bytes gave ["a"]. With strict=true, the input was rejected with a misleading message ("expected end of input"), or, for a key, with parse_error.112 instead of 110. Either reading of the lead byte leaves the message incomplete: a string at the end of a message must be terminated by 0xFF, so the lead byte cannot belong to a following message. Report parse_error.110 (unexpected end of input) for strings and keys, as the comment on get_bon8_string() already requires and as the reference decoder (HikoGUI) does. Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-02 07:47:50 +02:00
Niels Lohmann	11e75a5428	Cancel CI runs of merged and closed pull requests (#5748 )	2026-10-01 10:53:10 +02:00
Niels Lohmann	9d44e3f359	Merge branch 'develop' into json-view/02b-float-parser Conflicted only in tests/src/unit-class_lexer.cpp, where develop's #5737 lint fix (CAPTURE(x); -> CAPTURE(x)) collided with this PR's rewrite of the Eisel-Lemire float tests; kept the PR's new tests and applied the lint-fixed CAPTURE style. single_include regenerated via make amalgamate. Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-01 08:53:02 +02:00
Niels Lohmann	e400780533	Re-amalgamate single_include (#5745 ) * Re-amalgamate single_include #5737 changed 13 headers under include/ but merged without the matching single_include/nlohmann/json.hpp update, so the amalgamated header still had, among others, the GCC C++20 -Wignored-attributes pragma block and the clang -Wdocumentation push/pop that #5737 removed, the forwarding from_json tuple/array helpers it replaced with const references, and lacked the output_adapter char_traits changes it added. Regenerated with `make amalgamate` (astyle 3.4.13). The diff is exactly `git diff `b54ed188e` `e5a89d671` -- include/` (164+/95-); json_fwd.hpp and json_literals.hpp were already up to date. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Run the amalgamation check on pushes to develop #5737 was merged 39 seconds after its last push, while its own check_amalgamation run was still queued (earlier runs had been cancelled by the concurrency group), so the stale single_include reached develop without any failing check. Also run the check on pushes to develop, without cancelling in-progress develop runs. The "save" job (PR number/author for the comment workflow) only runs for pull requests, the checkout falls back to github.sha, and comment_check_amalgamation.yml only comments for PR-triggered runs, since push runs have no PR and no "pr" artifact. Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-01 08:09:34 +02:00
Niels Lohmann	9d88ead578	Clarify that the strtold fallback substitutes the locale's decimal point Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-10-01 07:40:37 +02:00
Niels Lohmann	9c71689715	Convert long doubles under a multi-byte decimal point completely The strtold fallback, which is left only for long double formats that are not binary64 (x87, binary128), substituted the first byte of the locale's decimal point for '.'. Under a locale whose decimal point is longer than one byte, such as fa_IR.UTF-8 or ar_EG.UTF-8 (U+066B), strtold stopped there and the value was truncated at the decimal point. A longer decimal point is now put into a copy of the token. The test "locale with a multi-byte decimal point" now compares the long double values with those of the "C" locale; with x87 long doubles it failed before. Fixes #5660. Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-09-30 20:19:11 +02:00
Niels Lohmann	44ec53c77b	Convert float and double with the library's own correctly rounded parser float, double, and long double where it is IEEE-754 binary64 (MSVC, Apple arm64) are now converted by the library itself, correctly rounded and independent of the locale and of the C and C++ libraries: - The token is split into sign, significand w (at most 19 digits), and decimal exponent q, using the positions of the decimal point and the exponent that the scanners already recorded, so no character is classified again. - Clinger's fast path where w and 10^\|q\| are exact. - Eisel-Lemire otherwise, now templated for binary32 and binary64. - For tokens with more than 19 digits whose w and w + 1 round differently, an exact big-integer comparison with the midpoint between the two candidates (the digit comparison of fast_float, simplified). This replaces the separate token walks of Clinger's fast path and of Eisel-Lemire, the significant-digit gate that avoided the former, and, for float and double, std::from_chars and the locale-aware strtod. std::from_chars and strtold remain only for other long double formats (x87, binary128, double-double) and for types that are not IEEE-754. Values are bit-identical to before wherever the previous conversion was correctly rounded; tokens converted in a locale with a multi-byte decimal point are now also exact. Overflow still gives out_of_range.406, underflow a signed zero. convert_float() is the entry point for other parsers of JSON text: it converts like the lexer, without allocation for binary32/binary64. Tests: exact-bit tests for double and float (ties, subnormal and overflow boundaries, huge exponents, more digits than any midpoint), Eisel-Lemire for binary32, the round trips of 200,000 doubles and 100,000 floats without declines, 508 generated hard cases with the expected bits of both formats (float_hard_cases.hpp) through the converter and both scanners, and JSON-level overflow/underflow checks for double and float. The locale tests now check the values in a locale with a multi-byte decimal point. Docs: the statements that parsing uses strtod/strtof/strtold; the fast_float credit now names the digit comparison. Signed-off-by: Niels Lohmann <mail@nlohmann.me>	2026-09-30 20:19:11 +02:00