On 14/10/2024 16:56, Vladimir Minenko via Development wrote:
Effectively, I don't see much difference from the current situation, where we "pretend" that we require C++17 but in reality we just check that we can pass `-std=c++17` to the compiler. Any usage in Qt code of individual language/library features still requires protection, because they're not universally implemented.And because of this, I once asked to set up a nightly build with forced `-std=c++17`, e.g. https://testresults.qt.io/coin/integration/qt/qtbase/tasks/nightly1728750903 <https://testresults.qt.io/coin/integration/qt/qtbase/tasks/nightly1728750903>. We already had two cases when C++20-specific code was merged and the build failed only because of this. There is a notification email set on failures for this build. There are only people from The Qt Company so far on it. If someone else is interested, I would gladly change this and include other people ;-)
Do you mean that, before your request, *all* the builds were forcing C++20?It used to be the other way around: people commit C++17 code that breaks under C++20, and the lack of C++20 coverage in the CI would allow it, only to break on those developers who force 20-or-above locally.
Thanks, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - Trusted Software Excellence
smime.p7s
Description: S/MIME Cryptographic Signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
