On 18/11/2020 07.34, Lisandro Damián Nicanor Pérez Meyer wrote:
Possibly also:
assistant6 for reading Qt 6 help files when not using Qt Creator
designer6 for those not using Qt Creator and needing to use Qt 6 plugins
Offtopic, but I wonder how much those standalone apps are still being
On 23/11/2020 11:29, Lars Knoll wrote:
I've quickly implemented 3) and pushed it here. It's only missing docs.
https://codereview.qt-project.org/c/qt/qtbase/+/322900
(includes the rationale of why optional is the wrong datatype)
I like this approach.
Thanks, patch is ready for review now.
Hi,
On 23/11/2020 08:48, Fabian Kosmale wrote:
I think we should at least_somehow_ deprecate operator<; but I'm not sure if it should be a special deprecation macro, or a special one.
I'm guessing you meant generic / special. I'm more keen on keeping
everything deprecated, but with a special
> On 23 Nov 2020, at 09:57, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> On 22/09/2020 16:17, Thiago Macieira wrote:
>> And especially if there's no impact to how the user uses the API.
>>> 1)
>>> std::optional compare();
>>>
>>> 2)
>>> enum class Ordering { Less = -1, Equal = 0, Gre
Hi,
On 22/09/2020 16:17, Thiago Macieira wrote:
And especially if there's no impact to how the user uses the API.
1)
std::optional compare();
2)
enum class Ordering { Less = -1, Equal = 0, Greater = 1, Unordered = 0xff
};
Ordering compare();
3)
Implement a Qt replacement for std::partial_o
As some of you might have noticed on Saturday night, I enabled automatic
closure of "Need more Info" issues. Unfortunately I screwed the process up with
a slightly wrong JQL querry when sedding the sets. This caused about 750 issues
to be transitioned out of NMI. Essentially I failed to set the
