+1
-Teemu
> -Original Message-
> From: Development On Behalf Of
> Jani Heikkinen
> Sent: maanantai 10. toukokuuta 2021 11.30
> To: development@qt-project.org
> Subject: Re: [Development] Nominating Mikko Gronoff as approver
>
> +1
>
> - Jani
>
> ___
Am 10.05.2021 um 10:04 schrieb Fabian Kosmale:
Regarding the API: I think the most common pattern in Qt would be to
add a static get method to the private class.
@Arno: But would that accessor actually be enough for you? As in, do
you know in your case that the QVariant contains a QFuture? If yo
This maintenance break is DONE
From: Ville-Pekka Karhu
Sent: Monday, May 10, 2021 08:05
To: Qt development mailing list
Subject: Re: Monthly CI maintenance break - May (Mon 10th May 2021)
This maintenance break starts NOW
From: Vi
+1
- Jani
From: Development on behalf of Samuli
Piippo
Sent: Monday, May 10, 2021 10:07 AM
To: development@qt-project.org
Subject: [Development] Nominating Mikko Gronoff as approver
Hi all,
I'd like to nominate Mikko Gronoff as approver for the Qt Pro
Regarding the API:
I think the most common pattern in Qt would be to add a static get method to
the private class.
@Arno: But would that accessor actually be enough for you? As in, do you know
in your case that the QVariant contains a QFuture? If you get a generic
QVariant instead, you may stil
I was suggesting QtPrivate::, since QFutureInterface/QFutureInterfaceBase
aren’t public and access to QFuture’s d-ptr is not something we would want to
recommend generally, I don’t think the average user will need it.
But, of course, the exact API can be discussed.
Best regards,
Sona
From: Kons
Hi all,
I'd like to nominate Mikko Gronoff as approver for the Qt Project.
Mikko has been tirelessly working together with the release team to
make sure the embedded releases are always better than the last one.
Although he is not actively contributing to Qt code, having approver rights
would help
