On Monday, 20 May 2019 05:51:49 PDT Mutz, Marc via Development wrote: > Or maybe we don't disagree at all and Thiago would accept allocating > memory (or, by extension, anything that's noexcept(false)) as a very > good reason to have a nullptr d?
I hadn't thought of noexcept, but let's be clear: yes, move constructors must be noexcept. That might be the good reason why it can't reset to a valid state. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
