On Saturday 7 September 2024 18:31:27 CEST Marc Mutz via Development wrote: > Another thing I neglected to mention is that there are two distinct > steps here. The first is to change certain Q_ASSERT()s into Q_PRE() > (say) precondition checks that optionally throw on violation. This has > nothing to do with C++26/29 contacts.
And this proprietary solution of ours could be made so it throws for user- compiled inline code, but not for the same inline functions compiled inside the Qt libraries. In this case, I agree it can be done. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
