If the trait supported more than one value (e.g. for different error codes), for example std::expected could also use it. -----Ursprüngliche Nachricht----- Von:Jason McKesson via Std-Proposals <std-proposals_at_[hidden]> Gesendet:Mo 22.07.2024 16:31 Betreff:Re: [std-proposals] all bytes zero == null object An:std-proposals_at_[hidden]; CC:Jason McKesson <jmckesson_at_[hidden]>; On Mon, Jul 22, 2024 at 9:59 AM Thiago Macieira via Std-Proposals <std-proposals_at_[hidden]> wrote: > I'm pretty sure that an opt-in flag applied to the class is what was being suggested. Granted, he suggested it as some terrible piece of language syntax (as well as some frankly bizarre destructor behavior that would require a conditional branch at every destruction of such an object), but it was explicitly an opt-in thing that other classes could detect and use. -- Std-Proposals mailing list Std-Proposals_at_[hidden] https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals