[Development] QVariant::operator< deprecation fallout
fabian.kosmale at qt.io
Mon Nov 23 08:48:33 CET 2020
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. Regarding point 4: Unfortunately, it's not that easy: If userType is actually a built-in type, then QMetaType::hasRegisteredComparators returns false, and QMetaType compare will not work. I'm afraid that in this case you would actually have to call the deprecated operator< ; unless we provide a replacement functionality in 5.15.3.
 Though operator< would still behave different for floating point values than QVariant::compare, as the former does a fuzzy compare for floating point values, and the latter and a strict comparison.
The Qt Company GmbH
fabian.kosmale at qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
Von: Development <development-bounces at qt-project.org> im Auftrag von Giuseppe D'Angelo via Development <development at qt-project.org>
Gesendet: Sonntag, 22. November 2020 18:09
An: development at qt-project.org
Betreff: [Development] QVariant::operator< deprecation fallout
QVariant::operator< has been deprecated in 5.15 because its broken
semantics, unable to establish a strict weak order (as expected by
"operator<". cf. VALUE.16 of QUIP-19).
The problem with this deprecation is that it doesn't offer a
replacement. Users that are still on Qt 5.15 and want to get rid of
deprecation warnings won't be able to get rid of this one. (Whether they
do this in order to upgrade to Qt 6 or just to keep their codebase clean
Only Qt 6 introduced a replacement (QVariant::compare()).
== Solutions ==
1) Un-deprecate operator<. The operator has been broken since forever,
we're not going to fix it anyhow, we just expect users to understand its
limitations (e.g. only use it between QVariants containing the same kind
of data, for for instance in order to sort a model's data).
2) Change the deprecation macro to another one that isn't included in
5.15 deprecations -- rather, one has to opt-in for. The opt-in is
supposed to be used only when targeting Qt 6, and not by projects which
want to stay on 5.15.
(This kind of macro could be applied to any other similar deprecation in
Qt 5.15 that doesn't have a corresponding replacement.)
3) Actually add a replacement for operator<. Possibly something that can
be mechanically ported to Q6Variant::compare via search&replace.
4) At least document how to avoid the warning, i.e. how to compare
"safely" two QVariants. Is there enough public API for this?
a) compare the variants' userType(), different -> uncomparable
b) check QMetaType::hasRegisteredComparators(type), false -> uncomparable
c) call QMetaType::compare(v1.data(), v2.data(), v1.userType(), result)
and return *result
This should be almost identical in Qt 6 (only step b) doesn't exist).
Giuseppe D'Angelo | giuseppe.dangelo at kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
More information about the Development