Pedro had already reached out to me on my experience with this for myself and I
gave some helpful feedback at that time. Many folk have since here echoed those
points.
Reading the comments thus made, I would council those responsible for listening
to the feedback to do so without comment until
On Fri, 8 Dec 2023 15:33:04 +0100
Elias Steurer via Development wrote:
> Hi Volker,
>
> Thanks for the update on the Qt Contributors Summit. It's great to
> hear about the initiatives to make the contribution process smoother,
> especially for newcomers.
>
> However, while setting up a Gerrit
On Friday, 8 December 2023 18:51:19 PST Marc Mutz via Development wrote:
> I think we need to mandate that if you want qint128 support, then you
> must compile with gnu++NN, which is actually the default on both GCC and
> Clang. We seem to switch that off (-ansi on).
Now answering the point you
On Friday, 8 December 2023 18:51:19 PST Marc Mutz via Development wrote:
> After spending countless hours between Ivan and myself fighting GCC's
> mysteriously-vanishing support for __int128_t (= qint128),
> it turns out that with -ansi/-std=c++NN, not even the most basic of
> work:
Hi Volker and other interested readers,
I do agree with most of what you said. It is unrealistic to switch out
the current platform tomorrow. This would be a multi year process.
Wiki
In the current state the wiki is a mix of outdated and redundant
information. We had a great success
> On 8 Dec 2023, at 15:06, Jani Heikkinen via Development
> wrote:
>
> Hi!
> Qt 6.7 Feature Freeze will be in effect today. If your changes are ready and
> approved by the end of today, you can still continue staging those in 'dev'
> over the weekend. The plan is to branch from "6.7" to
Il 09/12/23 03:51, Marc Mutz via Development ha scritto:
After spending countless hours between Ivan and myself fighting GCC's
mysteriously-vanishing support for __int128_t (= qint128),
it turns out that with -ansi/-std=c++NN, not even the most basic of
work: std::is_signed_v is_false_! I
