On Thursday 29 August 2024 18:14:37 GMT-7 Ville Voutilainen wrote: > It's very unlikely to be anything other than an incompatible build.
I presume you are answering that for the standard library. If the standard library will have an incompatible build, then by definition ours that depends on the regular build is not compatible with it. > So, if you wish to add more noexcepts into our code where we don't > demonstrably desperately need them, > and those noexcepts are on narrow-contract functions, at least add > them with a macro. I don't see the point of restricting to performance-critical code. Either we use the macro everywhere where we apply a noexcept where preconditions exist, or we don't. Said macro should be tied to the precondition itself, if we can. I haven't looked at the syntax: can one macro in one location expand to preconditions- or-noexcept-or-both? -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
