On Thursday, 27 January 2022 16:49:22 PST Marc Mutz wrote:
> That would break projects that build their Qt themselves (embedded), and
> with C++17 (because, you know, compile times increase with every std
> version 🙂).
Ok, then we make it optional to turn back the clock and compile as C++17. But
Hi Thiago,
> On Thursday, 27 January 2022 13:35:54 PST Thiago Macieira wrote:
> > I think it's fine to make the check per OS. But we can't use the __cpp_lib
> > variables.
>
> Alternative: we use the __cpp_lib macros, but we assert they are set in a .cpp
> file for the platforms where binary compa
On Thursday, 27 January 2022 13:35:54 PST Thiago Macieira wrote:
> I think it's fine to make the check per OS. But we can't use the __cpp_lib
> variables.
Alternative: we use the __cpp_lib macros, but we assert they are set in a .cpp
file for the platforms where binary compatibility and ABI matte
On Thursday, 27 January 2022 11:54:37 PST Marc Mutz wrote:
> Hi Thiago,
>
> > So here's my counter-proposal:
> >
> > We allow C++17 and C++20 Standard Library types in our ABI provided:
> > * we update our builds, all of them, to build with C++20 by default
> > * the use of those symbols in the A
Hi Thiago,
> So here's my counter-proposal:
>
> We allow C++17 and C++20 Standard Library types in our ABI provided:
> * we update our builds, all of them, to build with C++20 by default
> * the use of those symbols in the ABI is NOT behind an #if __cpp_lib check
This limits our ABI on _all_ plat
> On 27 Jan 2022, at 18:14, Thiago Macieira wrote:
>
> On Thursday, 27 January 2022 08:53:31 PST Tor Arne Vestbø wrote:
>> I don’t know what other things you’re referring to, but just to clarify,
>> this is not the case for macOS. We build the binary Qt packages with as
>> recent of an Xcode (a
On Thursday, 27 January 2022 08:53:31 PST Tor Arne Vestbø wrote:
> I don’t know what other things you’re referring to, but just to clarify,
> this is not the case for macOS. We build the binary Qt packages with as
> recent of an Xcode (and corresponding toolchain) as we have available in
> the CI,
> On 27 Jan 2022, at 17:19, Thiago Macieira wrote:
>
> We know a great deal of our users use the binary builds by the Qt Company. In
> order to make those the most widely supported, they are compiled with the
> oldest compiler we still support.
I don’t know what other things you’re referrin
On Thursday, 27 January 2022 03:38:05 PST Marc Mutz wrote:
> The only difference would be that a C++20 project would require a C++20(or
> later)-build of Qt. The error upon failure to comply would be
> unspectacular: linker not finding a symbol in the Qt library.
That's the problem and the thing t
foremost among them are coroutines
Note that on OSX / Clang, coroutines is still in wrote:
Hi,
>
>
> C++20 brings several new library features that would be great to use in the
> Qt API, foremost among them are coroutines and std::span.
>
>
>
> Yet, both of these are, in a sense, type-era
> Did I understand you correctly that we
> - would still guard any such method with an #if __cplusplus >= ...,
More likely __cpp_lib_span, etc, but yes in principle.
> - would compile our shipped artifacts in C++20 mode on all platforms where
> this is possible
I presume that would be necessa
Hi,
I certainly would like to use vocabulary types like std::span in our API rather
sooner than later. I have some questions regarding your
proposal, though. Did I understand you correctly that we
- would still guard any such method with an #if __cplusplus >= ...,
- would compile our shipped arti
+!
From: Development on behalf of Richard
Gustavsen
Sent: Tuesday, January 25, 2022 9:38 AM
To: Qt development mailing list
Subject: [Development] Nominating Volker Hilsheimer as co-maintainer of Qt
Widgets
Hi all!
I would like to propose a change in the main
Hi,
C++20 brings several new library features that would be great to use in the Qt
API, foremost among them are coroutines and std::span.
Yet, both of these are, in a sense, type-erasure techniques, and therefore most
useful across ABI boundaries.
Traditionally, Qt has defined a set of mini
+1!
> On 25 Jan 2022, at 09:38, Richard Gustavsen wrote:
>
> Hi all!
>
> I would like to propose a change in the maintenance of Qt Widgets [1]. I’m
> the current maintainer of the module, but I’m happy to inform you that Volker
> Hilsheimer has agreed to join me as a co-maintainer. Volker is
15 matches
Mail list logo
