diff options
| author | Thiago Macieira <thiago.macieira@intel.com> | 2024-05-20 11:31:02 -0500 |
|---|---|---|
| committer | Thiago Macieira <thiago.macieira@intel.com> | 2024-05-21 18:25:02 -0500 |
| commit | 26a81bd4fb1f382b2b1652566652301cfe1270a2 (patch) | |
| tree | 45b8436c6ace284aa79891e37a6870433d325879 /tests/auto/tools/qt_cmake_create/testdata/qml_project/TestComponent.qml | |
| parent | 067f60f7927fa825b71eed9d94bc280dd70ccc5c (diff) | |
Issue introduced by a68e4f3b96a82a93898f381e8ddc7f50f9c89d40 ("Use the
new QMetaType API in QVariant") in 6.0, which removed the d.is_null
reset at the same time as it replaced the std::destroy_at /
std::construct_at pair with an assignment operation.
[ChangeLog][QtCore][QVariant] Fixed a bug that would allow the class to
keep returning isNull() = true even after calling setValue().
Fixes: QTBUG-125472
Pick-to: 6.5 6.7
Change-Id: If05cb740b64f42eba21efffd17d13f6b1e8113c2
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Christian Ehrlicher <ch.ehrlicher@gmx.de>
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Diffstat (limited to 'tests/auto/tools/qt_cmake_create/testdata/qml_project/TestComponent.qml')
0 files changed, 0 insertions, 0 deletions