From what I see, the open questions from the thread in May are still:
- (paraphrasing Ville) which C++ 20 features are worth breaking (primarily
embedded) users who want new Qt version but don’t yet have the compilers that
can give them these facilities?
Hi,
For Qt 6.8 we continue to work on Phase 1 item
https://bugreports.qt.io/browse/QTBUG-109360. In other words we will not
mandate C++20 compilers in Qt 6.8 yet. An LTS release is not the right for such
a breaking change anyway. The possible releases for such a drastic change are
6.9 or
On 03.02.24 18:13, Thiago Macieira wrote:
> On Wednesday, 21 December 2022 09:51:52 PST Vladimir Minenko via Development
> wrote:
>> We got four user stories on Qt Bug Reports:
>>
>> 1. Use C++20 code with Qt - https://bugreports.qt.io/browse/QTBUG-109360
>> 2. C++20 is required for the
On Wednesday, 21 December 2022 09:51:52 PST Vladimir Minenko via Development
wrote:
> We got four user stories on Qt Bug Reports:
>
> 1. Use C++20 code with Qt - https://bugreports.qt.io/browse/QTBUG-109360
> 2. C++20 is required for the development of Qt itself -
>
On Thursday, 4 May 2023 06:48:55 PDT Volker Hilsheimer via Development wrote:
> But those that can and do upgrade their toolchain regularly might just as
> well upgrade to something fairly recent whenever they do that. Between 6.8
> branching (the last LTS only requiring C++17, as per current
> On 3 May 2023, at 19:20, Thiago Macieira wrote:
> On Wednesday, 3 May 2023 08:56:07 PDT Volker Hilsheimer via Development wrote:
>> However, C++23 adds a bunch of improvements, and perhaps it’s a much smaller
>> challenge for compiler vendors to support after C++20. If we stick to the
>>
Thiago Macieira (3 May 2023 19:20) wrote:
> I don't see us adopting Modules any time soon, not even for the 6.9
> release. It's not well supported *today*.
Also, they're a radical change to how source is organised and it "might
not be a bad idea" to wait until the C++ world has developed some
On Wednesday, 3 May 2023 08:56:07 PDT Volker Hilsheimer via Development wrote:
> The standing proposal is to move to C++20 with Qt 6.9, after the next LTS
> release. I see no pressing reasons to accelerate that. The value of the
> features Thiago listed - which excludes all the big stuff anyway -
Bumping this thread up in your inboxes as it includes the links to the JIRA
tickets where the journey towards C++20 has been planned and discussed so far.
Let's try to build on what we already know.
The standing proposal is to move to C++20 with Qt 6.9, after the next LTS
release. I see no
Hello all,
I want to share on this mailing list a proposal for the timeline and phases to
support C++20 with and in Qt. Writing this, I’m aware that there were other
discussions about the support of C++20 on this mailing list. This message is a
step to get a list of features that all Qt users
10 matches
Mail list logo
