Il 09/02/24 15:45, Volker Hilsheimer via Development ha scritto:
So, as much as I’d like for some of the things I’m working on to be able to benefit from C++ 20, I’d also say that we should rather slow down, and only require C++20 if we have something to show for it. We can perhaps still make improvements to better enable C++20 features, such as std::ranges, in application code; but that should neither require Qt to be built with C++20, nor require applications that don’t use std::ranges to use C++20.
An orthogonal but related question, do we see any advantage at requiring a C++20 build of Qt in order to use C++20 features with it? Insofar we've provided C++20-related APIs as entirely inline (under #ifdef protection, plus some export-relating shenanigans -- Q_POST_CXX17_API and so on). I'm not sure if somewhere we'd really like to move stuff out of line and thus require a C++20 build of Qt if you want to use those features.
My 2 c, -- 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: Firma crittografica S/MIME
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
