the personal conversation because I
suspected that
minGW acts differently and uses the system charset. However, I did some more
testing, and it seems that I was wrong.
So, I also think that no further action is required at this point.
Best regards,
Ivan
--
Ivan Solovev
Sen
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
ink that QASV(char) providing a broken UTF-8 sequence makes sense.
We also have
QString s('\xe4'); // calls QString(QChar) c-tor, using an implicit
QChar(char) c-tor
producing "ä", not an invalid UTF-8 sequence.
------
Ivan Solovev
Senior Software Engineer
The
rmatter.
IIUC, the problem of extra allocations is covered by the transcoding
iterators and views in the paper that was linked by Giuseppe.
Best regards,
Ivan
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt
atters, for one thing.
I must admit that I have no idea how this process works. How to reach out
to them and ask if they have any plans about char16_t support?
Maybe even asking if they have any plans for wchar_t -> char formatters
would be helpful.
Is there anyone familiar with the process?
B
here, so please
share your ideas!
Best regards,
Ivan
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft
+1
Best regards,
Ivan
From: Development on behalf of Alexey
Edelev via Development
Sent: Thursday, May 30, 2024 8:46 AM
To: development@qt-project.org
Subject: [Development] Nominating Dennis Oberst for approver rights
Hi all,
I would like to nominate
> The ABI functions can return one of these other types:
> bool (for equality comparisons)
> int (for non-partial ordering)
> QPartialOrdering (for partial ordering)
IIUC, returning QPartialOrdering is exactly what we want to avoid, due to the
std::partial_ordering -> QPartialOrdering (and
13.11.23 17:15, Thiago Macieira wrote:
> On Monday, 13 November 2023 01:34:08 PST Ivan Solovev via Development wrote:
>> Thiago wrote:
>>> The problem is that QPartialOrdering::Unordered has been in our ABI since
>>> 6.1 and we can't change that any more.
>>
Thiago wrote:
> The problem is that QPartialOrdering::Unordered has been in our ABI since 6.1
> and we can't change that any more.
Well, Marc already suggested a solution for this problem.
Let's just introduce Qt::{strong,weak,partial}_ordering and deprecate
QPartialOrdering
in favor of the new
Marc wrote:
> Why do you say it only applies to partial ordering? Do we already match
> the values, other than that of std::partial_ordering::unordered?
Yes, we do.
Thiago wrote:
> We can also just be evil and use bit_cast
Why is that evil? Reading about std::bit_cast, this can be an option, if
> I think it's acceptable for us to change the return type of a function so long
> as it's getting a new mangling.
Well, it would be easily achievable for the template methods, but not for the
inline hidden friend helper methods.
As immediate solution that comes to my mind is to add a third
+1
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
inuing with the patches, I'd like to hear more opinions.
Thanks,
Ivan
From: Ivan Solovev
Sent: Wednesday, October 4, 2023 11:15 AM
To: development@qt-project.org
Subject: Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)
So, let me give another
have a draft of a QUIP which describes how to apply the new macros
to the Qt classes: https://codereview.qt-project.org/c/meta/quips/+/490932
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
.
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB
not see any problems in
implementing `qCompareThreeWay` as (4).
Later we can also add `qComparesEqual` for consistency and even provide
3-arg overloads for string-like types, like Marc suggests.
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-S
you can use https://codereview.qt-project.org/c/qt/qtbase/+/479395 to
test the approach.
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, J
wap in Qt 6.5,
but here's the link to 6.2:
https://doc.qt.io/qt-6.2/qtalgorithms-obsolete.html#qSwap
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha
swap(lhs, rhs);
instead. So why should we act differently for comparison?
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Li
ring.
We already have `QTest::qCompare()`, so `Qt::qCompare` would not be
a much worse naming.
Anyway, it would be great to come to some kind of consensus about the
naming of the APIs, and move on to the actual implementation.
Best regards,
Ivan
----------
Ivan Solovev
Sen
Then, simply running this script to find and fix all deprecations in Qt MAJ.MIN
before creating the MAJ.MIN.0 branch should help.
I'm not sure how feasible it would be in practice, though.
Best regards,
Ivan
----------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Eric
ng, which then leads to a bunch of review comments about
code-style.
I think that it's better to give no hints, rather than misleading hints.
Best regards,
Ivan
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germa
+1
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
ros,
then the users will still need to implement all six (or 12 in case of
mixed-type comparison) relational operators instead of just calling one macro
and implementing two helper functions.
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
1
update the Jira ticket to keep them
in mind.
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: B
s() and Qt::compare() as public API for the users.
But then, if we use qt_*() functions, their names will not clash with any
of the existing APIs, and we can just let the end-users use these
functions directly.
[0]: https://codereview.qt-project.org/c/qt/qtbase/+/478199
n my
patches. Specially if it allows us to "unblock" compare() as a name for the
helper function.
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
www.qt.io
Geschäftsführer: Mika Pälsi,
Juha Va
_STRONGLY_ORDERED marco to simply expand into
operator<=>():
friend auto operator<=>(const MyType , const MyType ) noexcept
{ return order(lhs, rhs); }
Obviously, we want the helper function to remain the same for both C++17 and
C++20.
I don't see how we can re-use a compare
one-arg public equals)
This is not an ideal solution, because, as you can see in the output, the
operator==() explicitly calls the private static method instead of the hidden
friend. However, the generic code also works (this time calling hidden friend,
which forwards to private static).
Probably th
y exactly this issue.
And I must admit that it was rather difficult to detect it.
So, I think that this macro is useful.
Best regards,
------
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io
in my tests I only had issues with INTEGRITY, GCC 9.3.1 on OpenSuse 15.4,
and QCC 8.3.0 on QNX.
For these platforms the macro currently does nothing.
Best regards,
Ivan
--
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, G
rds,
Ivan
----
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io<mailto:ivan.solo...@qt.io>
www.qt.io<https://www.qt.io>
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
totally agree that we shouldn't merge something that is not 100% ready.
Best regards,
Ivan
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
ivan.solo...@qt.io<mailto:ivan.solo...@qt.io>
www.qt.io
Apart from the naming discussion, I consider the task to be almost done. At
least most of the other comments are addressed at this point.
Best regards,
Ivan
Ivan Solovev
Senior Software Engineer
The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
Hi!
+1 to all suggestions
Best regards,
Ivan
From: Development on behalf of Marc Mutz
via Development
Sent: Tuesday, May 9, 2023 8:51 AM
To: qt-dev
Subject: [Development] Proposing changes to https://wiki.qt.io/Qt_Coding_Style
Hi,
I'd like to propose the
Hi,
+1 to the approach suggested by Kai.
Having comments would be very helpful, but I do not think that we need a
separate comment field for each entry.
Best regards,
Ivan
From: Development on behalf of Kai Köhne
via Development
Sent: Tuesday, February 14,
Hi,
Should the example updates be picked to 6.5, or is it only a 6.6 thing?
Is there any general guideline from the Release Team?
Best regards,
Ivan
From: Development on behalf of Kimmo
Leppälä via Development
Sent: Wednesday, January 18, 2023 10:51 AM
To:
Hi Jani,
I'm not sure that I understand your proposal.
Currently we have FF on the 9th of December, and the release in March. So, it's
roughly 3 months between FF and release.
Now you propose to shift FF to January (I assume, also around 10th ), and the
release to April. That gives the same 3
Hi Thiago,
> Now at https://codereview.qt-project.org/c/qt/qtbase/+/444222
Thanks for sharing it!
> In fact, I came up with a better solution yesterday after sending this email:
move the support to QUuid. This allows us to have the new (mostly) source-
compatible API in place and simply move
Hi Thiago,
> I was working on extended integers and added qint128 and quint128 to qglobal.h
(qtypes.h)
Can you provide a link to your WIP patch? I tried to search but couldn't find
it in gerrit.
> it's used in the API, with a constructor and a toUInt128(), but that's
all. It's also not
> 1. It doesn't, obviously. If you emit signals, any signal argument must
>be owning, or QueuedConnection cannot be used. Given that C++20
>requires us to mark up views and non-owning ranges (enable_view,
>enable_borrowed_range), I'm confident that we could detect attempts
>to
Hi Marc,
>> I would like to know how that is supposed to work in practice. We have a
>> lot of public API dealing with Qt containers all over. What are you
>> going to do to, for example, to
>>
>> void addActions(const QList );
>>
>> in qwidget.h? What should it look like when we're done and
Hi
> Also the machinery of QT_DEPRECATED_METHOD(method, major, minor, reason)
> expanding to nothing for some settings, and possibly different things
> for other settings, of QT_DEPRECATED_WARNINGS_SINCE and
> QT_DISABLE_DEPRECATED_BEFORE entails (thanks to the limitations of the C
>
> If it can be done with little effort, including cherry-picking fixes
> backwards,
> even to 5.15, then it might be something to be investigated.
Well, at least with qt positioning we need to handle all the cherry-picks to
5.15 manually,
because the cherry-pick bot obviously does not detect
+1
Best regards,
Ivan
From: Development on behalf of Jaroslaw
Kobus
Sent: Wednesday, April 6, 2022 2:22 PM
To: Edward Welbourne ; Alex Blasche
Cc: development@qt-project.org
Subject: Re: [Development] Nominating Ievgenii Meshcheriakov for approver
+1
Hi Timur,
could you also update https://wiki.qt.io/Maintainers accordingly?
Best regards,
Ivan
From: Development on behalf of Timur
Pocheptsov
Sent: Monday, November 8, 2021 3:55 PM
To: qt-dev
Subject: [Development] Change in the maintainership of QtNetwork
Created https://bugreports.qt.io/browse/QTQAINFRA-4624
Thanks for pointing that out.
Best regards,
Ivan Solovev
Senior Software Engineer
The Qt Company
Erich-Thilo-Str. 10 12489
Berlin, Germany
www.qt.io<http://www.qt.io>
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Si
://codereview.qt-project.org/qt/qtpositioning
The init-repository script in the dev branch can also be used to set up the
repo properly.
Please target all QtPositioning-related patches to the new repository.
Best regards,
Ivan Solovev
Senior Software Engineer
The Qt Company
Erich-Thilo-Str. 10 12489
Hi,
I'd like to request a new repository on codereview.qt-project.org.
Name: qt/qtpositioning
Description: Qt Positioning module
Responsible persons: Alex Blasche (alexander.blas...@qt.io) and Ivan Solovev
(ivan.solo...@qt.io)
This is needed to ensure that QtLocation module development can
50 matches
Mail list logo
