On Sunday, 20 November 2022 18:38:08 PDT Thiago Macieira wrote:
> ("QString: replace #if with if constexpr...") and ending at
> https://codereview.qt-project.org/c/qt/qtbase/+/386952 ("
> QString::toLatin1: do the same as..."). The first six commits are merely
> clean- ups and reorganisation.
>
>
On Monday, 24 July 2023 05:34:58 PDT Ivan Solovev via Development wrote:
> > Why doesn't "equals" work?
> >
> > We've been over this in the code review: our current naming conventions
> > would dictate "equals" even for two arguments, as the most common
> > phrasing is "A equals B" instead of "A a
Hi,
let me try to revive the discussion, because we want the C++20 comparison task
to be finished for Qt 6.7.
> > And we have the calling convention:
> > lhs.O(rhs);
> > Qt::O(lhs, rhs); // if you know the type
> >
> > using Qt::O;
> > O(lhs, rhs);
> > . // if you don't
>
I've realized that my example in the email is somewhat out-of-date since 6.6
has been branched. To clarify the gap-filling behavior, if you specify an older
branch, the bot will fill gaps up to and including the latest feature branch.
The bot will fill gaps for missing feature branches (6.6), an
**As a developer, you do not need to change how you use the "Pick-to:"
footer.** You can stop reading here if you don't care too much about the
details. ;)
Over the past few years with the automatic cherry-picking, a common issue has
emerged: lost and forgotten cherry-picks. When the cherry-pi
