Niels Lohmann c864df3341 Spell out the move rationale at every handle_value(std::move) site ...

The comment explaining why the value is moved sat only on
json_sax_dom_parser::string(), and the callback parser's string() pointed
at it with "see json_sax_dom_parser::string()". That reference cannot be
searched for - the function is declared as `bool string(string_t& val)`
inside the class, so the qualified name appears nowhere - and the two
binary() overloads, which have always moved, carried no explanation at all.

Put the same comment on all four sites and name json_sax, which is
greppable, instead of a member that is not.

Comment-only; no generated code changes.

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

2026-09-05 10:25:01 +02:00

..

binary_reader.hpp

Fix CBOR tag handlers not recognizing tags 0-5 and 21-23 (#5331)

2026-08-19 20:19:47 +02:00

input_adapters.hpp

Require a container's value_type to match what data() points at

2026-09-05 10:24:38 +02:00

json_sax.hpp

Spell out the move rationale at every handle_value(std::move) site

2026-09-05 10:25:01 +02:00

lexer.hpp

Skip the float fast path when it cannot succeed

2026-09-05 10:24:42 +02:00

number_parse.hpp

Guard <charconv> include with __has_include for GCC 7

2026-09-05 10:24:19 +02:00

parser.hpp

📝 fix docs (#5217)

2026-06-29 22:15:18 +02:00

position_t.hpp

📄 adjust year (#5044)

2026-01-01 20:00:39 +01:00

string_scan.hpp

Buffer serializer output and add ensure_ascii string fast path

2026-09-05 10:24:44 +02:00