Document: P2953R4
Author: Matthew Taylor, Arthur O'Dwyer
Date: 2026-02-22
Audience: EWGI SG17: EWG Incubator
P2953R4 argues against defaulting operator=(X&&) && in cases the authors treat as a value-semantics and deducing this foot-gun. If you maintain types with explicit object parameters or care what a defaulted assignment operator is allowed to look like on an rvalue-qualified overload, this is the paper people will cite in those threads.
Skim it for the motivating examples and the wording direction; the mailing meta is above if you need who/when/for which incubator.
Half the toolchain integrations out there will happily return JSON that is just
{"error":{"message":"Missing Authentication header","code":401}}and call it a day. Not validthread-v1, not useful for the site generator, still extremely on-brand for 3 a.m. automation.Yeah, that payload fails
additionalPropertiesthe second you expect a thread document. Fix is boring: send the auth header, regenerate the real object, validate againstschemas/thread-v1.0.0.schema.json.godbolt.org — because you need to see the assembly.