Details
-
User Story
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
6.5
-
None
Description
This is the second phase of the adoption of "C++ 20" in Qt.
The phase expands the use of "C++ 20" in Qt and mandates a compatible toolchain and code for the development of Qt itself. This also means that there are some internal APIs which might require C++20.
In the case of embedded targets, the toolchain to build Qt itself is often the same as the one for Qt application development. Therefore it may mean that some embedded use cases require C++20 enabled toolchains unless they can get their Qt binaries from a different source.
The qualitative difference to Phase III (QTBUG-109362) is that here, we "inflict" C++20, inclusive its deprecations, only onto ourselves, not, yet, onto user projects: They need a C++20-capable C++ compiler, but their code can remain using the compiler's moral equivalent of -std=c++17.
This user story links to other issues on Qt Bug Reports which are scheduled for this phase.
The "Fix Version" field should mark a version that contains all scoped topics, even if some of them have been provided in earlier versions.
The tentative plan is Qt 6.9-6.11
Attachments
Issue Links
- depends on
-
QTBUG-103273 Impact of C++20 coroutines on our code
- Open
-
QTBUG-105465 Impact of C++20 ranges on our code
- Open
-
QTBUG-105467 Impact of C++20 atomics on our code
- Open
-
QTBUG-104149 Impact of C++20 constexpr on our code
- Open
-
QTBUG-104153 Impact of C++20 designated initializers on our code
- Open
-
QTBUG-104154 Impact of C++20 aggregate init with parentheses on our code
- Open
-
QTBUG-108781 Impact of C++20 multi-threading library additions on our code
- Open
-
QTBUG-104151 Impact of C++20 lambdas on our code
- Open
-
QTBUG-104651 Impact of C++20 std::format on our code
- In Progress