[Development] Switching Qt default builds to C++20 where supported
Thiago Macieira
thiago.macieira at intel.com
Tue Nov 26 17:58:38 CET 2024
On Monday 28 October 2024 09:14:43 Pacific Standard Time Thiago Macieira wrote:
> Of course.
>
> But you understood my general goals and, so long as I keep to them as Volker
> is requesting, neither you nor anyone else had a problem.
Update:
Re: https://bugreports.qt.io/browse/QTBUG-131575
even before I made any changes (and I'm not sure I would have enough time),
looks like Microsoft beat us to the punch: you CANNOT mix C++17 and C++20 in a
static build of Qt with MSVC. You must choose a single option for ALL your
code.
This changes the premise I made: that users didn't have a business choosing
the C++ version.
That being the case, I'm just not going to do anything. Not my problem any
more to move us forward. That also means I will not be doing the work to test
our headers in C++23 mode either - that's SEP again.
My concerns regarding ABI remain and will continue to block anything that
would offer C++20 content to users that expands to too-much inline code
(std::format, for now).
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCAI Platform & System Engineering
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5152 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20241126/f81720e6/attachment.bin>
More information about the Development
mailing list