Niels Lohmann eed5792dbd json_view: no per-object allocations in ordered_json comparisons ...

For an object type that keeps the order of its members (ordered_json),
resolve_indices() allocated a vector per compared object, and
resolve_members() two. They now use one working vector owned by equal(),
whose capacity is reused, and resolve_indices() needs none when the keys
are unique. resolve_members() sorts small objects by insertion, as the
other paths do.

Instructions per comparison (callgrind, GCC 13 and clang 18, x86-64):
twitter, ordered_json view == ordered_json: 0.939 / 0.941; 20000 small
objects with a duplicate key: 0.741-0.768; all other rows (json,
citm_catalog, canada, view == view) within 0.988-1.003.

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

2026-10-25 21:56:14 +01:00

..

json_fwd.hpp

Scan strings with SSE2, SSSE3, or NEON (#5853)

2026-10-21 20:00:50 +02:00

json_literals.hpp

Move the user-defined string literals to <nlohmann/json_literals.hpp> and add JSON_NO_AUTOMATIC_UDLS (#5610)

2026-09-30 20:08:17 +02:00

json_view.hpp

json_view: no per-object allocations in ordered_json comparisons

2026-10-25 21:56:14 +01:00

json.hpp

Fix VS 2015 build of the DOM parser (#5882) (#5916)

2026-10-25 12:08:58 +01:00